Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396)

The way it is currently framed, a worker can block the activate task by e.waitUntil(new Promise({})) which holds up the entire queue. It would be better to remove Step 13-14 from the atomic constraints and have them check that the registration hasn't started uninstalling and the active worker is still valid. 

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/396#issuecomment-73318943