Re: [w3c/ServiceWorker] Central algorithm for updating service worker state and registrations (#1416)

If things were implemented as spec'd, you'd get an event per task for related things. Eg if you have two registration objects representing the `ServiceWorkerRegistration`, things like `updatefound` would happen in different tasks per objects. It's now part of the same task.

Same if a worker becomes `activating` which also results in a controller change, and the previous worker becoming `redundant`. Those will now be dispatched in the same task whereas it was previously three tasks.

Using a single task for events that are part of the same action seems to make sense. As for the exact event order, I'm open to tweaking that if all browsers seem to behave the same way.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1416#issuecomment-498677995