Clarification on what happens during a terminated activation

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!

Start by reading the activation algorithm in the linked Service Worker specification and compare its note with the Chrome, Firefox, and Microsoft Edge behaviors described here. Review the issue discussion to determine whether the specification needs clarification and what agreed wording or behavior would constitute completion.