| Summary: | Sandboxed iframes don't fire DOMContentLoaded | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Matt Bierner <matb> | ||||
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bfulgham, cdumez, webkit-bug-importer, wilander | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | Safari 13 | ||||||
| Hardware: | Mac | ||||||
| OS: | macOS 10.15 | ||||||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=33604 https://bugs.webkit.org/show_bug.cgi?id=209653 |
||||||
| Attachments: |
|
||||||
|
Description
Matt Bierner
2020-08-17 15:24:05 PDT
The same also seems to happen for the `load` event. This continues to behave as reported. Chrome says "Blocked script execution" in console, but the event actually gets dispatched. Seems pretty bad, as there is no reasonable way to detect that a sandboxed frame is done loading in WebKit, so this just prompts authors to add otherwise unnecessary allow-scripts. |