Re: [ServiceWorker] why does Register algorithm step 5.3.1 check for an active worker? (#856)

I guess proceeding with update could allow the waiting worker or soon-to-be installed worker to become .active, in case someone does register().then(wait for an active version).

However, Chrome's current impl looks it'll only do that if the new worker is different than the waiting worker.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/856#issuecomment-202224680