- From: Matt Falkenhagen <notifications@github.com>
- Date: Tue, 24 Mar 2015 23:23:35 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Wednesday, 25 March 2015 06:24:04 UTC
Technically, I don't think the service worker can be "recovered" once it reaches redundant state, what would happen is another service worker (with possibly the same script) would be installed and activated. Anyway, what is left to do here? I don't recall the details of the decision to make the worker that fails to activate still the active worker, and I'm not sure whether the current spec is aligned with that decision... Chrome has a crash bug if you fail activation after claiming, so I'm planning to fix that as per the current spec (as of b4ad5e9): the worker will relinquish its controllees upon activation fail, and will track the spec as we go. Also, it seems right to fire "controllerchanged" in this case, no? --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/659#issuecomment-85870202
Received on Wednesday, 25 March 2015 06:24:04 UTC