Re: [w3c/ServiceWorker] consider Client behavior for windows where initial about:blank is replaced with a loaded document (#1091)

> The primitive needs to reflect that to be honest about what is really happening.

I agree. Just want to make sure it doesn't get more complex than needed.

> Do you mean a new reserved client that is different from the about:blank initial document client?

Yes.

> Which client does the final document end up with?

The about:blank client.

> Either way you are suggesting that the client ID for a global change during its lifetime. That seems like a bad invariant to break.

The client IDs aren't changing. In the fetch event, devs will see both the client and the reserved client, but the reserved client will be gone away when the navigate completes in this case. I mean only the about:blank client with its initial ID will be alive. I think it isn't odd as that's what happens.

In this case, the reserved client is just used during the main resource fetch for matching a service worker, queueing postMessages, etc. I think the messages sent to the reserved client should be requeued to the about:blank client when the document is installed.

-- 
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/1091#issuecomment-309674982