Re: [w3c/ServiceWorker] Should the worker be removed from the registration *before* its state is set to "redundant"? (#1273)

As a general rule, we should ensure that the following properties are updated:

* `installing`/`waiting`/`active` on registration objects.
* `state` on service worker objects.

…before notifying the developer that any of those things have changed. Our current notifications are:

* `updatefound` event on registration objects.
* `statechange` event on service worker objects.
* `navigator.serviceWorker.ready`.
* `install`, `activate` event on the service worker global.

I'll review the spec for this, and ideally come up with a system that enforces the above.

-- 
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/1273#issuecomment-498575637