Re: [w3c/ServiceWorker] Inconsistencies due to when clients are created (#870)

@jungkees 

> There's still a possibility that the active worker of the registration can be changed from the first matching attempt and the second matching attempt. That is, in that occasion, the main resource and its subresources are served by two different service worker versions. @jakearchibald, I'd like to clarify if this would be okay.

Yeah, that's fine. You opt in to dealing with that when you use `skipWaiting`.

> We may need client.used

Agreed!

> In #870 (comment)'s "New Window Navigation" case, targetClientId may be the client for initial about:blank instead of undefined

I was chatting to @annevk in #whatwg and he suggested that `about:blank` doesn't get a fetch client in this case, it uses the parent's.

-- 
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/870#issuecomment-245574595