- From: Matt Falkenhagen <notifications@github.com>
- Date: Sat, 27 Oct 2018 00:28:57 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 27 October 2018 07:29:18 UTC
F2F: This and related issues was discussed at the F2F, see a summary at https://github.com/w3c/ServiceWorker/issues/1303#issuecomment-432967494
I'll add that if we're removing resurrection then having unregister({force: true}) would provide a means of avoiding the new worker stomping on the storage of an old but still used worker.
--
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/1292#issuecomment-433598608
Received on Saturday, 27 October 2018 07:29:18 UTC