Re: [slightlyoff/ServiceWorker] Add a way to detect reloading only client (#872)

> Client lifetimes overlap when reloading a page, so at the "navigate" request after pressing reload, there will appear to be two clients (or just the old one because clientId is null? not clear on this)

I think there should only be one client, as Firefox reports https://github.com/slightlyoff/ServiceWorker/issues/870. 

> I don't think the existing isReload property tells you much, since it doesn't appear to tell you anything about other clients.

I think we should drop `isReload` https://github.com/slightlyoff/ServiceWorker/issues/873 - what do you think?

> For example maybe the "navigate" fetch event could have previousClientId.

I think this should just be `clientId` https://github.com/slightlyoff/ServiceWorker/issues/817#issuecomment-206396683

> There would probably need to be a non-null clientId

We're calling this `potentialClientId`, because it may never exist.

> I know that my SW will serve a document that replaces the previous client

You don't if the `potentialClient` is going to replace a completely different client to the request's `client`, as would happen with the target attribute of links. We need something like `targetClient` I think.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/872#issuecomment-208031854