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

I feel a bit unconfortable about making the SW matching affect the decision of the client reuse. I think they are orthogonal, and adding that behavior sounds like we make another edge case behavior.

> The natural answer is "clear the controller" if the final load does not make a scope.

I think this makes sense complying with the "navigation matching always wins" rule.

> Nowhere else in the system do we allow a client to go from controlled to uncontrolled.

Firing a `controllerchange` event to `navigator.serviceWorker` when clearing the controller would work?

---

Another edge case is when an iframe navigates to a non-initial about:blank document. I think this is a normal cross-origin navigation case where the non-initial about:blank document lands on a newly created client with a SW set to null. But when it navigates from an initial about:blank to a non-initial about:blank, I'm not sure whether we should keep the normal behavior or special case it to use the inherited controller.

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