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

Until we settle on something I'm going to be doing the minimal amount of code changes to meet the sanity conditions of:

> 1. The initial about:blank should be controlled by the parent's service worker. And:
> 2. The final document load should not be controlled by any service worker if its URL does not match a scope?

In this lame first version in gecko the controller will appear to get reset, the page will share its global, and the Clients API will see a different client ID for the final loaded page.  This approach is not what I recommend as a spec solution, but I didn't want to write significant code until we agreed on a direction.  Its a corner case that is only really observable under some very precise conditions, so I don't think this will be a problem in the short term.  

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