Re: [ServiceWorker] What is the "Doom Installing Worker" algorithm supposed to be doing? (#847)

I guess if we assume everything in the lifecycle job code runs on a single thread its not technically "racy", but I still don't understand the algorithm.  I don't see how the .installing worker could ever be set on the registration by the front job in "Doom Installing Worker" since that requires loading a worker script asynchronously.  It seems like Doom Installing Worker would just always exit at step 5.

---
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/847#issuecomment-197023923