Closed
Bug 1531885
Opened 6 years ago
Closed 6 years ago
RTCPeerConnection constructor exceptions related to RTCCertificate aren't surfaced properly
Categories
(Core :: WebRTC: Signaling, enhancement, P3)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla69
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: bwc, Assigned: bwc)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We do throw exceptions like this:
But, they aren't surfaced correctly, because this happens in an async function. The promise is stored, but the RTCPeerConnection constructor does not throw when this happens:
Assignee | ||
Updated•6 years ago
|
Rank: 25
Priority: -- → P3
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → docfaraday
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
Try looks good.
Assignee | ||
Comment 4•6 years ago
|
||
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/28fa2a88940e
Surface certificate-related errors in RTCPeerConnection's c'tor, fix an error type, and re-enable a test. r=jib
Comment 6•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in
before you can comment on or make changes to this bug.
Description
•