Re: [w3c/ServiceWorker] what happens if an initial about:blank inherits a controller, but its navigation request does not match any service worker? (#1232)

FWIW, here is the gecko bug to handle this:

https://bugzilla.mozilla.org/show_bug.cgi?id=1419620

> The other option would be to try to change the spec model of iframe loading such that the case above creates a document with the scope2/index.html URL to start with, and it's not controlled to start with. I believe that IE/Edge do something like that. Doing that would require some careful thought and compat testing and so forth though....

The initial about:blank stuff is already rife with interop problems.  I really don't think I have time to take this sort of thing on.

I'd like to proceed with disabling global re-use when going from controlled to uncontrolled for now.  Its a somewhat niche case and seems the safest thing to do for now.

-- 
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/1232#issuecomment-346393925