Re: [w3c/ServiceWorker] clarify behaviour of `AbortSignal` in `FetchEvent::respondWith` (Issue #1662)

saschanaz left a comment (w3c/ServiceWorker#1662)

It seems https://wpt.fyi/results/service-workers/service-worker/fetch-event-network-error.https.html?label=master&label=experimental&aligned&q=fetch-event covers it? Basically passing an aborted fetch is equivalent to passing a rejected promise, which is what's done [here](https://github.com/web-platform-tests/wpt/blob/288431ce29951f071aee0ff38c69001b7bfb0e82/service-workers/service-worker/resources/fetch-event-network-error-worker.js#L8).

But per [the iframe](https://github.com/web-platform-tests/wpt/blob/c3825813d925f9b40d49ebf537e7045a92e9a3a9/service-workers/service-worker/resources/fetch-event-network-error-controllee-iframe.html#L4) we only check if it rejects but without checking the error interface.

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

Message ID: <w3c/ServiceWorker/issues/1662/3755557467@github.com>

Received on Thursday, 15 January 2026 15:59:02 UTC