Open Bug 1625984 Opened 6 years ago Updated 1 year ago

Need a JS warning when answerer rejects a bundle

Categories

(Core :: WebRTC: Signaling, enhancement, P3)

Product:
Core
Component:
WebRTC: Signaling
Type:
enhancement

Tracking

()

People

(Reporter: bwc, Assigned: bwc)

Details

REMB is broken in the non-bundle case until we can update webrtc.org (see bug 1576576, and even that we aren't sure will fix it), and transport-cc is going to have similar problems (see comments in bug 1606823). We should probably log a warning if the answerer doesn't bundle all m-sections, so developers have a heads-up.

Assignee: nobody → docfaraday
Severity: normal → S3

This should be a bit easier since we added this:

https://searchfox.org/mozilla-central/rev/4fcb729dc98138af00570c0a378fbff90a167d79/dom/media/webrtc/jsapi/PeerConnectionImpl.cpp#2088

We'd still need to teach JsepSession to be able to return warnings as well as errors.

Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.