Re: [w3c/ServiceWorker] Experimenting with abortable algorithms (#1443)

> We still need to define what happens to in-flight fetches etc.

@jakearchibald for both the killswitch or for `unregister({ immediate: true })`? Even for the later, if we are immediately getting rid of the entire registration, is there anything special we would need to do within the algorithm to abort? For fetch, can we simply [drop the task and fallback to network](https://github.com/w3c/ServiceWorker/pull/1440/files#diff-27b79860afe28f01aed4f1f6228367faR2832)?

When aborting individual algorithms and keeping the registration, I think it makes sense to ensure the algorithms are clear on how to safely abort without corrupting the rest of the service worker state. If we are already getting rid of the entire registration, I'm don't see how that's necessary.

-- 
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-505933707