This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 547
Navigation should be based on Fetch. #548
Comments
mikewest
added a commit
to w3c/webappsec-csp
that referenced
this issue
Aug 1, 2016
This introduces a new 'navigation check', which we'll need to wire up to HTML. That, in turn, requires HTML to use Fetch. WHATWG's does, W3C's does not (w3c/html#548).
Talking with @estark37 a moment ago, referrer policy is another concrete example of a spec that this is going to block: see the series of patches that landed in WHATWG's HTML to resolve w3c/webappsec-referrer-policy#40. |
Note that this is going to block CSP as well, due to the various navigation hooks we need (see whatwg/html#1619). |
Thanks, we'll aim to port these changes in. Aiming for part of 5.2 is the most likely target. |
Wonderful, thank you @adanilo! |
Ping. |
Reviewing this now |
Current 5.2 WD references fetch. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Compare https://w3c.github.io/html/browsers.html#navigating-across-documents to https://html.spec.whatwg.org/#navigate. The latter calls into Fetch for processing, the former doesn't. This makes it pretty hard to port changes like whatwg/html#1230.
It would be helpful if the W3C version of this document picked up navigation-related changes to ensure that we don't have to write these kinds of hooks twice.
The text was updated successfully, but these errors were encountered: