Re: [ServiceWorker] unregister() then register() same-scope, different script URL that fails: what do you expect to happen? (#396)

Thanks for the clarification Jungkee, this is what Chromium is doing (rather, it will be once https://code.google.com/p/chromium/issues/detail?id=445151 is fixed).

In addition to FIFO order, Chromium does "make all the others block until the first one is done" behavior. The one exception is that a running register job waiting in the 'installing' state gets aborted whenever another register job for that scope is scheduled to run later in the queue. This stops waitUntil(new Promise({}) from blocking the queue.

Also, as Michael mentioned, Chromium also coalesces multiple sequential calls with the same inputs into one job in the queue.

I believe all of these are acceptable as per the spec.

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