- From: Ben Kelly <notifications@github.com>
- Date: Tue, 04 Jun 2019 06:51:09 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 June 2019 13:51:31 UTC
The statechange stuff at least matches what I implemented in firefox: https://searchfox.org/mozilla-central/rev/f8b11433159cbc9cc80500b3e579d767473fa539/dom/serviceworkers/ServiceWorkerRegistration.cpp#396-489 Firefox does not run the updatefound event in the same task currently, but is guaranteed to be after the statechange events. So that kind of matches here. I'm unsure of the controllerchange event right now. Getting all this right in the face of cross-process implementations is pretty tricky and I spent a lot of time getting firefox to match the current tests. I expect anything that changes behavior may have a high implementation cost to adjust to. I just want to make sure we're not making behavioral changes that don't have a solid reason to avoid churning implementations. -- 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-498680149
Received on Tuesday, 4 June 2019 13:51:31 UTC