Re: [whatwg/fetch] Consider splitting `document` into `document` and `nested-document`. (#755)

Since Request.destination was only relatively recently shipped in browsers, now might be the time to make this change.  Sites would need to adapt, but they could do `evt.request.destination.includes('document')` or something.

FWIW, this better matches what firefox uses internally:

https://searchfox.org/mozilla-central/rev/292d295d6b084b43b70de26a42e68513bb7b36a3/dom/base/nsIContentPolicy.idl#87-96

Which we then map to the exposed `document` destination:

https://searchfox.org/mozilla-central/rev/292d295d6b084b43b70de26a42e68513bb7b36a3/dom/fetch/InternalRequest.cpp#274-277

I was wondering if this change would interact badly with the [portals proposal][], but I guess the navigation request would have to complete well before any portal is promoted from 3rd party to 1st party.

[portals proposal]: https://github.com/KenjiBaheux/portals/blob/master/explainer.md

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/755#issuecomment-394707588