Chrome won't load CSS sourcemaps in an iframe

[Daniel Schaffer]

Why won't chrome won't load CSS sourcemaps within an iframe? Repro here: http://run.plnkr.co/NaAndt5tc4JcuqIA/

Both the parent page and the child page in the iframe reference the same CSS file, which includes a sourcemap reference. However, if you look at the pages in the inspector, it only uses the sourcemap when inspecting elements from the parent. Elements from the child only reference the css file. Firefox will show sourcemaps for both the parent and the iframe, why doesn't Chrome?

[PhistucK]

The URL seems to have expired.

☆PhistucK

On Sat, May 28, 2016 at 9:50 PM, Daniel Schaffer <d...@dandoes.net> wrote:

Why won't chrome won't load CSS sourcemaps within an iframe? Repro here: http://run.plnkr.co/NaAndt5tc4JcuqIA/

Both the parent page and the child page in the iframe reference the same CSS file, which includes a sourcemap reference. However, if you look at the pages in the inspector, it only uses the sourcemap when inspecting elements from the parent. Elements from the child only reference the css file. Firefox will show sourcemaps for both the parent and the iframe, why doesn't Chrome?

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/4f4c38e3-4678-42b5-8a73-473bd0906843%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Schaffer]

Doh!

Okay, here's a plunkr link: http://plnkr.co/edit/htFjDVeT7h3XYqbR8u6n?p=preview

Since it all runs in iframes, in order to see the issue, you'll need to click the blue "expand" icon in the upper right of the preview pane so it opens in a new window.

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/18d3ef52-cf2a-4bac-9427-ffbde82882ee%40googlegroups.com.