- From: Matt Falkenhagen <notifications@github.com>
- Date: Mon, 23 Nov 2015 22:31:20 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Tuesday, 24 November 2015 06:31:53 UTC
Chrome behavior is a bit wrong here: it immediately terminates an exiting worker instead of waiting for it to finish processing events. If we do get in a situation where we dispatch a fetch event and then immediately the next worker calls skipWaiting(), it looks like we'd forcibly kill the worker in the middle of onfetch(). We have a TODO to actually wait. --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/785#issuecomment-159169463
Received on Tuesday, 24 November 2015 06:31:53 UTC