Open
Bug 1765811
Opened 4 years ago
Updated 10 months ago
WPT failure: a rejection from underlyingSink.abort() should be preferred to one from underlyingSource.cancel()
Categories
(Core :: DOM: Streams, defect, P3)
Core
DOM: Streams
Tracking
()
ASSIGNED
People
(Reporter: saschanaz, Assigned: saschanaz)
References
(Blocks 1 open bug, )
Details
(Whiteboard: dom-lws-bugdash-triage)
Bug 1734241 didn't fix it for some reason.
| Assignee | ||
Comment 1•4 years ago
|
||
Per https://searchfox.org/mozilla-central/rev/6f6cf2810742d32454251afdb8e632c27999bea7/dom/streams/ReadableStreamPipeTo.cpp#240 it seems to mock Promise.all but then it doesn't seem to actually look at the order of promises. I'll try writing a test for that specific function if not already exist.
| Assignee | ||
Comment 2•4 years ago
•
|
||
Okay, it's not Promise.all. cancel() is indeed being called first. (ReadableStreamCancel calls cancel() synchronously but WritableStreamAbort calls abort() asynchronously)
| Assignee | ||
Updated•4 years ago
|
Assignee: nobody → krosylight
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•4 years ago
|
||
The abort steps seemingly should not call the cancel callback synchronously? 🤔
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
| Assignee | ||
Updated•10 months ago
|
Whiteboard: dom-lws-bugdash-triage
You need to log in
before you can comment on or make changes to this bug.
Description
•