Re: [w3c/ServiceWorker] Accept-CH frame duplicates fetch events and preloads (Issue #1810)

asutherland left a comment (w3c/ServiceWorker#1810)

Do we know if anyone is working to make progress on "Merging Client Hints Infrastructure into FETCH (and HTML) Standards" https://github.com/whatwg/fetch/issues/1398?  It seems like these are fundamental issues that fetch needs to be involved in, and fetch has handled similar-ish issues like HTTP basic auth and TLS client certificate dialogs where each [request has an associated traversable for user prompts](https://fetch.spec.whatwg.org/#concept-request-window) which then is [explicitly used in http-network-or-cache-fetch to process a 401 status](https://fetch.spec.whatwg.org/#ref-for-concept-request-window%E2%91%A6) or [TLS certificate dialogs in http-network fetch](https://fetch.spec.whatwg.org/#ref-for-concept-request-window%E2%91%A0%E2%91%A0). 

cc @annevk and @yoavweiss who both were involved in (duping to) the above issue.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1810#issuecomment-3967751504
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1810/3967751504@github.com>