Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266)

> (I'm trying to investigate whether sites that would break)

Thanks for checking this.

> But I don't quite get how the semantics changed: even with resultingClientId, clientId for navigations is non-existent/null/empty and it seems that could be validly expressed as empty string or null.

By introducing `resultingClientId`, I thought we'll set `clientId` for a navigate request to the [source browsing context](https://html.spec.whatwg.org/#source-browsing-context)'s active document's environment's id. (See https://html.spec.whatwg.org/#process-a-navigate-fetch step 2 where the request is set up. `FetchEvent.clientId` is set to request's client's id later in Handle Fetch.) So, I think changing from null to the empty string wouldn't reflect the semantics we'll have in the final behavior.

-- 
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/1266#issuecomment-361860845