Re: [whatwg/fetch] Add request's reserved client (#383)

> So how can this be an environment settings object? Isn't this information what's used for the eventual creation of one?

I defined an algorithm setting up and returning an environment settings object that has different algorithms than those of browsing context/worker's environment settings object: https://github.com/whatwg/html/pull/1776/commits/df5262bf83f7f10b5620f14b625b29b3c5987cd0#diff-36cd38f49b9afa08222c0dc9ebfe35ebR77922
The reserved client's id will be used to set the actual environment settings object's id when it's created later. Also, I wanted it to be a type of an environment settings object as we should be able to enumerate these client objects in the service worker steps: `get(id)`, `matchAll()`, etc.

> Also, if a reserved client knows the target browsing context, should we still provide that as a slot?

The reserved client's target browsing context just returns request's target browsing context which was set in https://html.spec.whatwg.org/#process-a-navigate-fetch step 2. The reason why reserved client should hold this information is that when a service worker gets this client later from `clients.get(id)` or `clients.matchAll()`, it won't have any reference to the original request. (We plan to use the state of the active document of the target browsing context for WinodwClient's properties associated with the reserved 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/whatwg/fetch/pull/383#issuecomment-246699422