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

That's right. I confirmed by testing Chrome reuses the global in the case shown in your previous comment.

> What do you think the various properties on FetchEvent should be for this situation?

To my understanding, the declaratively-defined-iframe case and the snippet in https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-300817825 go through the same flow according to the spec. I think the properties on FetchEvent should be the same. That is:

- client: about:blank
- reserved client: reserved environment for nested.html request (this is different from the f2f decision)
- target client: null (or even about:blank?)

So, devs will see two different clients (about:blank and reserved env) exist during the fetch, which is what's happening indeed. And when the resulting document is installed, the about:blank client is reused and the reserved client is abandoned. (If the navigate found a matching active service worker, that property should be overwritten to the client.)

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