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)

enhancement

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:

https://searchfox.org/mozilla-central/rev/00f3836a87b844b5e4bc82f698c559b9966e4be2/dom/media/PeerConnection.jsm#478

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:

https://searchfox.org/mozilla-central/rev/00f3836a87b844b5e4bc82f698c559b9966e4be2/dom/media/PeerConnection.jsm#450

Rank: 25
Priority: -- → P3
Blocks: 1533015
Assignee: nobody → docfaraday

Try looks good.

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
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: