- From: Asa Kusuma <notifications@github.com>
- Date: Wed, 12 Jun 2019 16:36:09 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 June 2019 23:36:31 UTC
@mattto Looking at your [force delete change](https://chromium.googlesource.com/chromium/src/+/fafebc8a59d87a8c6f0620a91ee7cb3a0d8331eb%5E%21/#F4), I see the following comment: > The rest of this function is similar to Clear() but is slightly different because this emergency deletion isn't part of the spec and happens outside of the normal job coordinator. Why are additional safeguards beyond [Clear Registration](https://w3c.github.io/ServiceWorker/#clear-registration-algorithm) required? Does the spec need an additional or expanded algorithm for being able to guarantee terminating a service worker? Related, should [Clear Registration](https://w3c.github.io/ServiceWorker/#clear-registration-algorithm) call `Remove scope to registration map` as well? `unregister()` is not the only entry point into `Clear Registration`. -- 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/614#issuecomment-501492521
Received on Wednesday, 12 June 2019 23:36:31 UTC