Implement RTCError for SDP parse errors
Categories
(Core :: WebRTC: Signaling, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox150 | --- | fixed |
People
(Reporter: bwc, Assigned: iamanshulmalik)
References
(Blocks 5 open bugs)
Details
(Keywords: dev-doc-needed)
Attachments
(2 files)
This covers the initial steps of adding RTCError and RTCErrorDetailTypes, refactoring JsepSession to be able to throw RTCError (as well as a plain DOMException), and filling out RTCError.sdpLineNumber.
Updated•3 years ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
I'd like to give it a try.
| Reporter | ||
Comment 2•1 month ago
|
||
The interop 2026 test-cases: https://wpt.live/webrtc/RTCError.html?interop-2026
| Assignee | ||
Comment 3•1 month ago
|
||
Adds the RTCError (DOMException subclass) and RTCErrorEvent (Event subclass)
interfaces as a prerequisite for plumbing RTCError through SDP, DTLS, SCTP,
and hardware encoder failure paths.
RTCError.sdpLineNumber and JsepSession integration are follow-up in this bug.
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
https://hg.mozilla.org/mozilla-central/rev/fdce8626e275
https://hg.mozilla.org/mozilla-central/rev/2c30cb9e11be
Updated•19 days ago
|
Comment 7•15 days ago
|
||
Was the omission of the dev-doc-needed keyword deliberate - i.e. is there a reason this should not be documented?
If it needs to be, please add that keyword because otherwise MDN doesn't get a trigger to do anything. Note that compatibility data got recorded already in https://github.com/mdn/browser-compat-data/pull/29352 - also I am assuming that this is shipped as well, since there is no obvious preference gating this.
| Reporter | ||
Updated•14 days ago
|
Description
•