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

Right now when `conrollerchange` fires the `.controller` property is always set and never `null`.  I'm worried sites would break if this invariant changes.

I think avoiding about:blank replacement would be less breaking because its unlikely many modern sites using service workers are actually relying on this feature.

Can we at least agree that:

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?

How we get from (1) to (2) is up for discussion.  For now, though, I'm testing for these.  I'm need to do something to make this happen.  I'm leaning towards doing the new global for now, but willing to change to a different system if we can decide on a clean way to do it.

Note, if we can spec a way to cleanly clear the controller we could also enable the case of immediate unregister() if the site opts into it.

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