Audit Error Messages, and make sure they're on par with JS Streams implementation
Categories
(Core :: DOM: Streams, task)
Tracking
()
People
(Reporter: mgaudet, Assigned: evilpie)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
We need to audit our Error messages and make sure that they're approximately on par with the JS Streams implementation.
(Mildly concerned we need to make sure we match them for compat reasons, but, 🤞🏻)
Assignee | ||
Comment 1•3 years ago
|
||
We definitely need to make some improvements to our error messages. We are worse than our old implementation and Chrome.
As an example:
new ReadableStream({ start(controller) { controller.close(); controller.close() } })
Firefox old: 'close' called on a stream already closing.
Chrome: Failed to execute 'close' on 'ReadableStreamDefaultController': Cannot close a readable stream that has already been requested to be closed
Firefox new: ReadableStreamDefaultController.close: Cannot Close
var stream = new ReadableStream(); stream.getReader(); new ReadableStreamDefaultReader(stream);
Firefox old: n/a (no ReadableStreamDefaultReader)
Chrome: Failed to construct 'ReadableStreamDefaultReader': ReadableStreamDefaultReader constructor can only accept readable streams that are not yet locked to a reader
Firefox new: ReadableStreamDefaultReader constructor: Stream is Locked
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
bugherder |
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Comment 7•3 years ago
|
||
Comment 8•3 years ago
|
||
bugherder |
Comment 10•3 years ago
|
||
bugherder |
Assignee | ||
Comment 11•3 years ago
|
||
All readable streams (excluding byte streams) error messages should now be in a good place. We can open a new bug for code we don't plan on shipping first.
Assignee | ||
Updated•3 years ago
|
Description
•