Re: [ServiceWorker] Race when registering multiple service workers for the same scope (#783)

> That option was considered but not proper to synchronize the Unregister with Register/Update where Unregister is effective only when all the clients are unloaded. That is, it's not practical for all the Register/Update requests coming from different tabs and Soft Updates in parallel to hold until the condition for Unregister is met.

Its fine to still use a flag on the registration to indicate an unregister is in progress without blocking.  I'm just saying a single queue to step through job state would be the easiest to understand and avoid the races we are seeing in the spec at the moment.

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