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

> @jakearchibald I think so, but it's not all defined in detail yet. Note that Fetch's current concept of target is a browsing context, not a client.

Yeah, but we use the same type (environment settings object) for **clients**. I think we should add an _id_ internal slot to environment settings object.

I think I need to define sort of a special environment settings object that has algorithms returning the values expected for reserved client during navigation (before the normal environment settings object is created.) And then when the normal environment settings object is created, the id of this new object is set to the id of the temporary environment settings object. From the script surface, `clients.get(id)` returns a `Client` object associated with either the temporary client or the created client depending on the state.

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