- From: Joseph Liccini <notifications@github.com>
- Date: Mon, 03 Dec 2018 16:20:27 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 December 2018 00:20:49 UTC
Hi! Across browsers, we are seeing different behaviors for a terminated activation. For Chrome: If a worker is terminated during activation, it is placed back into the 'activating' state on next browser load. The activation handlers are re-run. For FireFox: If a worker is terminated during activation, the worker is discarded, and re-installation is required. For Microsoft Edge: If a worker is terminated during activation, the worker (on next browser load) is placed into the 'activated' state. The activation handlers are not re-run. >From the spec: https://w3c.github.io/ServiceWorker/#activation-algorithm > Note: Once an active worker is activating, neither a runtime script error nor a *force termination of the active worker prevents the active worker from getting activated*. Chrome's behavior seems to be what I'd expect as a developer, but I don't think that it's well-reflected in the spec. Thoughts? Thanks! -- 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/issues/1372
Received on Tuesday, 4 December 2018 00:20:49 UTC