NEW 202625
Consider splitting request destination "document" into "iframe" and "frame". 
https://bugs.webkit.org/show_bug.cgi?id=202625
Summary Consider splitting request destination "document" into "iframe" and "frame".
Mike West
Reported 2019-10-07 00:46:34 PDT
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".
Attachments
Add attachment proposed patch, testcase, etc.
Ahmad Saleem
Comment 1 2025-02-16 20:40:20 PST
WebKit Source: https://searchfox.org/wubkat/rev/1f927bd4c630547d9a40efe5dd98ccd7fc337c93/Source/WebCore/Modules/fetch/FetchRequestDestination.idl#30 We still don't have `frame` and it is slightly outdated from web specification: https://fetch.spec.whatwg.org/#requestdestination
Radar WebKit Bug Importer
Comment 2 2025-02-16 20:40:43 PST
<rdar://problem/144963590>
Note You need to log in before you can comment on or make changes to this bug.