Bug 204615
| Summary: | Sandbox flags should be snapshotted at start of navigation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ian Clelland <iclelland> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, beidson, bfulgham, dbates, wilander |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ian Clelland
Document sandboxing flags should come from the state of the iframe container as the navigation starts. See recent HTML spec change at https://github.com/whatwg/html/pull/5098.
There are web platform tests as well, under review at https://github.com/web-platform-tests/wpt/pull/20411 -- Current results are available at https://wpt.fyi/results/html/browsers/sandboxing?label=pr_head&max-count=1&pr=20411
As far as I can tell, Safari's current behavior on those tests is:
* sandbox-navigation-timing: Fails because final document is sandboxed.
* sandbox-navigation-timing-2: Fails because final document has allow-same-origin.
* sandbox-navigation-timing-3: Fails (times out) because final document does not allow scripts.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |