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

> After that change, the expectation is clientId is always set to a string value initialized in HTML.

Just to clarify, I think there will be cases where its still not set.  For example, a user opening a new tab and navigating to a URL will not have any `clientId` for the navigation `FetchEvent`, correct?  There is no current Client to populate the value.

I think its a little unclear what happens for `window.open()`, `iframe.src`, `clients.openWindow()`, etc, but the intention was for those to have a populated `clientId`.

-- 
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-361962166

Received on Wednesday, 31 January 2018 15:13:47 UTC