[BUG]: Broken styling in plot rendered in an iframe
@nathell ci sta già lavorando.
Dal 21/1/2026.
- Lingua principale
- JavaScript
- Stelle
- 18.3k
- Fork
- 2k
- Merge medio
- 2g 12h
- PR unite (30g)
- 28
Descrizione
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:
As compared to correct rendering:
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.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.