[Webkit-unassigned] [Bug 204615] New: Sandbox flags should be snapshotted at start of navigation
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Nov 26 06:18:22 PST 2019
https://bugs.webkit.org/show_bug.cgi?id=204615
Bug ID: 204615
Summary: Sandbox flags should be snapshotted at start of
navigation
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: DOM
Assignee: webkit-unassigned at lists.webkit.org
Reporter: iclelland at chromium.org
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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191126/14dc7aad/attachment-0001.htm>
More information about the webkit-unassigned
mailing list