Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-09-19 11:20:09 +01:00
Code Issues Projects Releases Packages Wiki Activity

script: Do not start Fetch operations if they have been aborted by the AbortController (#39295)

Browse source 
The first step for aborting fetch calls. It only
has the case where the signal was already aborted
prior to fetch starting.

Part of #34866

Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
This commit is contained in:
Tim van der Lippe 2025-09-17 10:49:27 +02:00 • committed by GitHub
parent 6deb42dbd5
commit 6cba44e0e3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 49 additions and 92 deletions
Download patch file Download diff file Expand all files Collapse all files

78
tests/wpt/meta/fetch/api/abort/general.any.js.ini vendored
View file

@ -6,30 +6,6 @@
[general.any.html]
expected: TIMEOUT
[Aborting rejects with AbortError]
expected: FAIL
[Aborting rejects with AbortError - no-cors]
expected: FAIL
[Signal on request object]
expected: FAIL
[Signal on request object created from request object]
expected: FAIL
[Signal on request object created from request object, with signal on second request]
expected: FAIL
[Signal on request object created from request object, with signal on second request overriding another]
expected: FAIL
[Signal retained after unrelated properties are overridden by fetch]
expected: FAIL
[Already aborted signal rejects immediately]
expected: FAIL
[Request is still 'used' if signal is aborted before fetching]
expected: FAIL
@ -51,15 +27,6 @@
[Call text() twice on aborted response]
expected: FAIL
[Already aborted signal does not make request]
expected: FAIL
[Already aborted signal can be used for many fetches]
expected: FAIL
[Signal can be used to abort other fetches, even if another fetch succeeded before aborting]
expected: FAIL
[Underlying connection is closed when aborting after receiving response]
expected: FAIL
@ -93,12 +60,6 @@
[Readable stream synchronously cancels with AbortError if aborted before reading]
expected: NOTRUN
[Aborting rejects with abort reason]
expected: FAIL
[Signal on request object should also have abort reason]
expected: FAIL
[response.bytes() rejects if already aborted]
expected: FAIL
@ -108,30 +69,6 @@
[general.any.worker.html]
expected: TIMEOUT
[Aborting rejects with AbortError]
expected: FAIL
[Aborting rejects with AbortError - no-cors]
expected: FAIL
[Signal on request object]
expected: FAIL
[Signal on request object created from request object]
expected: FAIL
[Signal on request object created from request object, with signal on second request]
expected: FAIL
[Signal on request object created from request object, with signal on second request overriding another]
expected: FAIL
[Signal retained after unrelated properties are overridden by fetch]
expected: FAIL
[Already aborted signal rejects immediately]
expected: FAIL
[Request is still 'used' if signal is aborted before fetching]
expected: FAIL
@ -153,15 +90,6 @@
[Call text() twice on aborted response]
expected: FAIL
[Already aborted signal does not make request]
expected: FAIL
[Already aborted signal can be used for many fetches]
expected: FAIL
[Signal can be used to abort other fetches, even if another fetch succeeded before aborting]
expected: FAIL
[Underlying connection is closed when aborting after receiving response]
expected: FAIL
@ -195,12 +123,6 @@
[Readable stream synchronously cancels with AbortError if aborted before reading]
expected: NOTRUN
[Aborting rejects with abort reason]
expected: FAIL
[Signal on request object should also have abort reason]
expected: FAIL
[response.bytes() rejects if already aborted]
expected: FAIL