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

Do we have an idea which tests will change?

Chrome also does most things in separate tasks. Each change is typically its own IPC, and each IPC is its own task. So Chrome acts like Firefox in that statechange is one task and controllerchange is another. Chrome also doesn't have a good system yet of changing all the JS objects first and then firing the events. Not really sure yet how difficult it would be to change these.

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

Received on Tuesday, 4 June 2019 15:03:27 UTC