Re: [w3c/ServiceWorker] ready promise is kind of weird with overlapping scopes (#1278)

>  We're already doing similar signaling for statechange events and controllerchange events.

Right and it's a bit tricky in our implementation already to send the signals in the right order. For example we have to send the "change to active" message before the "resolve ready promise" message, to ensure inside the ready.then() that registration.active is populated. It'll be more complex to ensure .ready resolves at the right time when the registration changes (due to unregistration or new registartion).

It's all doable but it could be tricky to get it right, and there could be some unavoidable races.

-- 
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/1278#issuecomment-366890492