[w3c/ServiceWorker] should blob URL clients have their controlled updated if their parent's controller is changed? (#1265)

Currently we inherit the service worker controller from the parent client for blob URL windows and workers.  We don't, however, do anything to handle the case where the parent's controller is changed after the blob URL is created.  This can happen in only two ways right now:

1. A service worker calls `skipWaiting()` and replaces an existing active worker.
2. A service worker calls `clients.claim()`.

Currently the spec will update the controller on a blob URL client in case (1).  The spec updates does "For each service worker client client who is using registration:" which should include blob URL clients.

For claim, however, it attempts to match the service worker's scope against the client's creation URL.  This will never match for blob: URL clients.

Should we consider propagating a controller change from a parent to the blob URL child client?

-- 
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/1265