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

In Schedule Job step 2.3, the given job (Job_B here for example) is enqueued if it is not [equivalent](https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#dfn-job-equivalent) to the last job (Job_A) in the queue. So, it was the only case that seemed to matter when Job_B has the same scope and a different script url with Job_A. This means, Job_B has to wait until Job_A finishes no matter how long Job_A's installing takes (e.g. caching big files, etc.) knowing that it eventually will replace Job_A's registration anyway.

If this is an edge case and doesn't seem bad, I agree to remove DoomInstallingWorker.

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