[w3c/ServiceWorker] should sec-ch-ua headers be visible in FetchEvent.request.headers (#1525)

Currently the spec requires that user-agent header be set after the service worker fetch handler, so the user-agent header is not visible on `FetchEvent.request`.

Client hints headers in general, however, are added prior to service worker processing:

https://wicg.github.io/client-hints-infrastructure/#fetch

This results in the new sec-ch-ua headers appearing on `FetchEvent.request` which seems inconsistent with not exposing user-agent.

What do folks think we should do here?  Accept the difference between sec-ch-ua and user-agent?  Align sec-ch-ua with current user-agent behavior?

@annevk @jakearchibald @youennf

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