Re: [w3c/ServiceWorker] Should we expose reserved clients? (#1216)

> As soon as it can be messaged/navigated. I'm sure it's more nuanced than that though.

In previous discussions reserved became non-reserved at execution ready time.  This is at least a spec'd point in time for each global (although implementations may vary in reality of course):

https://html.spec.whatwg.org/#concept-environment-execution-ready-flag

> Right now, client.get(doesntExist) will resolve with undefined, so that was my first thought.

So, delayed resolution until we detect the global for `reservedId` is being discarded and then we resolve null at that point?

I guess that's feasible.

-- 
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/1216#issuecomment-339696999