plotly / plotly/plotly.js

[BUG]: Broken styling in plot rendered in an iframe

未关闭
#7,688 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@nathell 已经在做这个了。

开始于 2026年1月21日。

bug
主要语言
JavaScript
星标
18.3k
派生
2k
平均合并
2 天 12 小时
30 天内合并 PR
28

描述

Description

A plot rendered within an iframe (same-domain, i.e. with access to the iframe’s dom) has broken styling when Plotly is loaded and runs from within the root document’s context.

This happens because Plotly attempts to add styles to the parent document, even when the plot div belongs to a child document: addRelatedStyleRule gets the HTMLStyleElement from document, rather than from graphDiv.ownerDocument.

Screenshots/Video

Broken rendering within iframe – note the misaligned title and mispositioned, always-visible modebar:
Image

As compared to correct rendering:
Image

Steps to reproduce
  • Create and open a file with this content:
<html>
  <body>
    <iframe id="content" style="width: 800px; height: 600px;"></iframe> <!-- Remove for just the reference rendering -->
    <script src="https://cdn.plot.ly/plotly-3.3.1.min.js"></script>
    <script>
      const doc = document.getElementById('content').contentDocument; // Replace with just `const doc = document;` to see the reference rendering
      doc.write('<div id="plot" style="width: 600px; height: 400px;"></div>');
      const plot = doc.getElementById('plot');
      Plotly.newPlot(plot, [{x: [1, 2, 3, 4, 5], y: [1, 2, 4, 8, 16]}], {title: {text: "Some plot"}});
    </script>
  </body>
</html>
  • Note wrong styling as per screenshot
  • Follow comments to compare with the correct rendering
Notes

My use case is to render Plotly graphs correctly in a Storybook-like component library (Portfolio, for ClojureScript). Portfolio renders components within iframes, which triggers the issue. I have a workaround that clones the element and associated styles from <style id="plotly.js-style-global"> to the iframe's document after the plot is rendered – this works, but is clunky.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。