- From: Philip Jägenstedt <notifications@github.com>
- Date: Mon, 11 Jun 2018 02:30:36 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 11 June 2018 09:31:00 UTC
I haven't read through this thread, but came here from https://chromium-review.googlesource.com/c/chromium/src/+/1066919 and just want to make sure one facet ends up being covered. There, `window.open` is used after receiving the Accept-CH-Lifetime header, on the assumption that the requests for that new browsing contexts wouldn't get any client hint headers if not for the Accept-CH-Lifetime header. But as [discussed in that review](https://chromium-review.googlesource.com/c/chromium/src/+/1066919/2/third_party/WebKit/LayoutTests/external/wpt/client-hints/resources/accept_ch_lifetime.html.headers#1), it seems like there are only examples in the specs to go by, no normative requirements. So hopefully this issue will make it clear precisely which fetches get the headers :) -- 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/726#issuecomment-396181312
Received on Monday, 11 June 2018 09:31:00 UTC