Re: [ServiceWorker] A worker that fails to activate should relinquish its controllees (#659)

Hmm, I thought we'd decided that a ServiceWorker that fails to activate is still active (in fact, it's active at the start of activation).

The problem is the activation could have half-applied, leaving some data stores migrated and others not, so rolling back is likely to leave things just as boken. Unregistering is bad because you'll lose push registrations etc. I thought we were going to leave this as an exercise for the developer?

Is the current pattern to leave the registration with a null active state? When would it next pick up an update? (was there a discussion around this I missed?)

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/659#issuecomment-85495915