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

Once an origin is crossed as part of a redirect, the reserved client must be discarded and a new one created for the other origin.

In terms of clients that cross service worker scopes, I think that's fine, even if multiple service workers queue messages for that client.

@wanderview 

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

I was thinking the promise would resolve with the real (not-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/w3c/ServiceWorker/issues/1031#issuecomment-270397802