Re: [w3c/ServiceWorker] Kill resurrection (#1415)

It's worth noting that this surfaces more of the weirdness in `navigator.serviceWorker.ready`.

1. Register SW.
1. await `navigator.serviceWorker.ready`.
1. Unregister & reregister.

Now you're in a state where `navigator.serviceWorker.ready` has settled, but the service worker in your scope isn't actually ready.

-- 
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/1415#issuecomment-498253842