Re: [w3c/ServiceWorker] Should Cache#addAll reject with AbortSignal's reason if the signal is already aborted? (Issue #1684) from Anne van Kesteren on 2023-07-26 (public-webapps-github@w3.org from July 2023)

From: Anne van Kesteren <notifications@github.com>
Date: Wed, 26 Jul 2023 02:05:35 -0700
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/issues/1684/1651292197@github.com>

Hey @CYBAI, thanks for raising this!

It seems that none of `addAll()` accounts for the fact that each request can be aborted. I agree that it would make sense to adhere to the same logic as `fetch()` uses and propagate the first exception thrown.

@shaseley can you review this for Chromium?

@asutherland can you review this for Gecko?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1684#issuecomment-1651292197
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1684/1651292197@github.com>

Received on Wednesday, 26 July 2023 09:05:42 UTC