Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031)

> A way around this is to provide a way to get a genuine client from a reserved client - a promise that would resolve with a client or undefined if the client isn't created or goes cross-origin.

A `Client.ready` promise seems reasonable to me in practice, but it might be a bit clunky given that `Client` is a snapshot.  The promise would resolve, but `Client.reserved` would still return true.

Personally I'd be happy to make `Client` a live object in the future, but I think there were implementation concerns around that in blink.  (Or perhaps I am thinking of the issue that drove us to have FetchEvent.clientID instead of the Client itself on the event.)

-- 
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/1031#issuecomment-267979220