Re: [w3c/ServiceWorker] Should Cache#addAll reject with AbortSignal's reason if the signal is already aborted? (Issue #1684)

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

Agreed.  This is also consistent with the naming of [Promise.all()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all) which also rejects on the first rejection with the first rejection reason.  (Versus [Promise.allSettled](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/allSettled) which will provide all rejections.)

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

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