Re: [w3c/ServiceWorker] Central algorithm for updating service worker state and registrations (#1416)

> That seems totally reasonable given that a worker cannot transfer between registrations.

Its a little bit wonky because there are cases where a document may have a ServiceWorker object, but not have its corresponding ServiceWorkerRegistration object.  For example, a client receives a postMessage from the SW and so have the msg.source attribute.  My solution ends up creating the ServiceWorkerRegistration even though its not exposed in these cases.

-- 
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/pull/1416#issuecomment-499122999