1396922 - Implement |setCodecPreferences| in RTCRtpTransceiver

Status: RESOLVED FIXED

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

Comment 1

[Bulk Bug Changes for mreavy's org]

Mass change P2->P3 to align with new Mozilla triage process.

Comment 2

[Jim Mathies [:jimm]]

Low priority currently.

Comment 3

[Thomas Wisniewski [:twisniewski]]

Chrome is also passing the related WPT.

Comment 4

[Dan Baker[:dbaker]]

Attachment: Bug 1396922 - Implement |setCodecPreferences| in RTCRtpTransceiver;r?bwc,jib

Comment 5

[Dan Baker[:dbaker]]

We will want to target landing this at the start of the 128 Nightly to ensure this has enough time to bake in. Given that this feature required adjustments to our codec negotiation logic we want to ensure no obvious issues arise from it. The main concern is with sites possibly doing feature detection for setCodecPreferences and using a new code path not previously used by Firefox.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c9bfe7c044aa
Implement |setCodecPreferences| in RTCRtpTransceiver;r=bwc,jib,webidl,smaug

Comment 7

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/46235 for changes under testing/web-platform/tests

Comment 8

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/c9bfe7c044aa

Comment 9

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot

Comment 10

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot

Comment 11

[Dan Baker[:dbaker]]

Release Note Request (optional, but appreciated)
[Why is this notable]: This allows for WebRTC services to easily manipulate what codecs it wishes to receive and the preferred order.
[Affects Firefox for Android]: Yes
[Suggested wording]: The setCodecPreferences method allows applications to disable the negotiation of specific codecs (including RTX/RED/FEC). It also allows an application to cause a remote peer to prefer the codec that appears first in the list for sending.
[Links (documentation, blog post, etc)]: https://www.w3.org/TR/webrtc/#dom-rtcrtptransceiver-setcodecpreferences, https://blog.mozilla.org/webrtc/ (blog should be coming)

Comment 12

[Ryan VanderMeulen [:RyanVM]]

Added to the Fx128 relnotes.

Comment 13

[Hamish Willee]

FF128 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/33981