Implement RTCError for DataChannel/sctp failures
Categories
(Core :: WebRTC: Signaling, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
Updated•3 years ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
•
|
||
Interop 2026 does not directly include RTCError, but it does include test-cases in RTCDataChannel-close.html that are failing for lack of this.
Nevermind, missed this because there is a single test case in RTCError.html that isn't in interop 2026.
| Assignee | ||
Comment 2•6 months ago
|
||
Note: RTCErrors of this kind can be thrown at RTCDataChannel, and those can be on workers, but the spec only exposes the interface on Window. That's probably a spec bug. I've filed https://github.com/w3c/webrtc-pc/issues/3092
Updated•5 months ago
|
| Assignee | ||
Comment 3•2 months ago
|
||
It looks like this will mainly clear up failures here:
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
Updated•1 month ago
|
Comment 7•1 month ago
|
||
Reverted this because it was causing mass failures.
| Assignee | ||
Comment 9•1 month ago
|
||
Actually, RTCError probably should be exposed on DedicatedWorker rather than Worker, for consistency with RTCDataChannel.
Comment 10•1 month ago
|
||
Comment 11•1 month ago
|
||
Comment 12•1 month ago
•
|
||
Backed out for causing gtest failures @SetLocalAnswerInHaveLocalOffer.
- Backout link
- Push with failures
- Failure Log gtest
- Failure log mochitest
Comment 13•1 month ago
|
||
Comment 14•1 month ago
|
||
| bugherder | ||
Updated•1 month ago
|
Updated•24 days ago
|
Comment 16•21 days ago
|
||
FF155 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/45175
Description
•