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

> Queued fetches aren't really the issue. It's more fetches that are in progress, as in the request has been made, or is in progress.

Even if an HTTP request is already in progress, can we not just drop the task? Like if the user agent gets the response, and the requesting task no longer exists, is that not gracefully handled? Not sure if it's possible to have an underlying assumption that, by default, any running service worker task can simply be dropped that the user agent will gracefully fail any dependent tasks cc @mattto @wanderview @asutherland

What does step 5 of [Terminate service worker](https://www.w3.org/TR/service-workers-1/#terminate-service-worker) do if there are running tasks, like fetch tasks?
> 5. Abort the script currently running in serviceWorker.

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