Consider splitting request destination "document" into "iframe" and "frame".
Categories
(Core :: DOM: Networking, enhancement)
Tracking
()
People
(Reporter: mkwst, Unassigned)
Details
As per the discussion in https://github.com/w3c/webappsec-fetch-metadata/issues/45, it seems reasonable for Fetch Metadata to expose a little additional granularity in a request's destination rather than the current "document" for top-level navigation and nested navigation.
https://github.com/whatwg/fetch/pull/948 proposes splitting the "document" destination into "iframe" and "frame" for nested navigation, mirroring "object" and "embed".
It's likely something y'all would want to poke at along with Fetch Metadata generally. Until that mechanism exposes the value to developers, there's not a huge reason to poke at this (though it will be visible in Service Workers that examine outgoing Request objects). ckerschb@ probably has a Fetch Metadata bug against which this can be marked as blocking?
|
||
Comment 3•5 years ago
|
||
Clearing out old ni?s at the moment. In the meantime we have added support for Sec-Fetch-* within Bug 1508292 and we support the proposed granularity of iframe and frame, see:
https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/dom/security/SecFetch.cpp#52
Description
•