Re: [whatwg/streams] Do the abort steps of ReadableStreamPipeTo really guarantee the abort callback to be called before cancel? (Issue #1229) from Taym Haddadi on 2025-12-06 (public-webapps-github@w3.org from December 2025)

From: Taym Haddadi <notifications@github.com>
Date: Sat, 06 Dec 2025 11:22:12 -0800
To: whatwg/streams <streams@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/streams/issues/1229/3620991951@github.com>

Taym95 left a comment (whatwg/streams#1229)

Hi all, any update on this? Chrome is currently the [only browser passing this test](https://wpt.fyi/results/streams/piping/abort.any.html?label=master&label=experimental&product=chrome&product=servo&product=firefox&product=safari&aligned), in https://github.com/servo/servo/pull/41035
I changed Servo to match Chrome, but the spec isn’t clear whether pipeTo is meant to sequence abort/cancel so that abort’s rejection always wins, or whether implementations may just let the first rejection win. It would be great to clarify which behavior is intended so we know whether the current WPT (and Servo’s change) are correct.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1229#issuecomment-3620991951
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1229/3620991951@github.com>

Received on Saturday, 6 December 2025 19:22:16 UTC