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

I have thought about this a bit more over the weekend.

Given the fact that we are making `Client.url` always empty string while reserved, the only issues to resolve here is the cross-origin `postMessage()`.  As Jake said, its desirable to have that work for same-origin.

So I now think it would be a bit better to keep the same reserved Client when a redirect is same-origin.  If a redirect cross origin boundaries then a new reserved Client would need to be created.

This solves the immediate problem and also make the window reserved Client consistent with the worker reserved Client during redirects.

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