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

We early exit if there is a newest worker and the script URL matches.  We don't check the state of the newest worker or if there is an active worker.

I guess I'm not opposed to the check for active, but want to understand why.

With the current unified queue spec language I think the only non-active state that could match would be an installed .waiting worker.  Why would we want .register() to re-download the script for a .waiting with same script URL, but not a .active?

---
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-202197254