Re: [w3c/ServiceWorker] clarify when FetchEvent.clientId will or will not be set for navigations (#1267)

I kind of like the simplicity of clientId just being empty/null for all navigations. Do we know if people are really asking for a non-empty clientId for these cases? We might just save ourselves time/complexity by sticking with empty/null.

The big use case I'm hearing for the new clientId stuff is to implement resultingClientId, so you can track the whole page load (main resource + its subresources).

I guess Workers are an interesting point, though.

-- 
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/1267#issuecomment-361976488

Received on Wednesday, 31 January 2018 15:56:23 UTC