1836519 - Inconsistent handling of errors in new Response(stream).text()

Status: NEW

(Core :: DOM: Streams, defect)

Description

[Kagami Rosylight [:saschanaz] (they/them) (OOO until 2024-10-06)]

new Response(new ReadableStream({
  pull(c) {
    c.error("oh"); // This causes an extra console message that cannot be read by JavaScript
  }
})).text() // DOMException: The operation was aborted.

new Response(new ReadableStream({
  pull(c) {
    throw "oh"; // extra console message as the first example does
  }
})).text() // DOMException: The operation was aborted. 

new Response(new ReadableStream({
  pull(c) {
    throw new Error("oh"); // No message
  }
})).text() // DOMException: The operation was aborted. 

new Response(new ReadableStream({
  pull(c) {
    c.error(new Error("oh")); // Also broken
  }
})).text() // DOMException: The operation was aborted.

Safari passes the original error message to DOMException for all cases while Chrome does not show it anywhere. We should at least be consistent here.

But perhaps the spec should use error.cause?

Comment 1

[Kagami Rosylight [:saschanaz] (they/them) (OOO until 2024-10-06)]

This doesn't block the conversion, it can keep the current behavior.