- From: Asa Kusuma <notifications@github.com>
- Date: Sun, 30 Jun 2019 20:40:56 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 1 July 2019 03:41:18 UTC
> Fetches that have the service worker as their client will terminate (since the fetch group is terminated. The fetch spec defines how this happens. But we don't use a client for things like service worker updates. re: Step 5 of `Terminate service worker`, Is the fetch group termination implicit or explicit? (I can't seem to find any explicit language around terminating fetch groups). Can we create a similar group construct for service workers? Either per origin or per registration. So that we can associate algorithms (like update) with the service worker group, and then transitively terminate everything in one swoop via the group. -- 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/pull/1443#issuecomment-507104762
Received on Monday, 1 July 2019 03:41:18 UTC