Closed Bug 1396922 Opened 7 years ago Closed 2 months ago

Implement |setCodecPreferences| in RTCRtpTransceiver

Categories

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

54 Branch
enhancement

Tracking

()

RESOLVED FIXED
128 Branch
Tracking Status
relnote-firefox --- 128+
firefox128 --- fixed

People

(Reporter: bwc, Assigned: dbaker)

References

(Depends on 1 open bug, Blocks 3 open bugs)

Details

(Keywords: dev-doc-complete, parity-chrome, parity-safari)

Attachments

(1 file)

      No description provided.
Rank: 25
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3

Low priority currently.

Severity: S3 → S4
Priority: P3 → P4
Blocks: 1829758

Chrome is also passing the related WPT.

Keywords: parity-chrome
Severity: S4 → S3
Priority: P4 → P2
Assignee: nobody → dbaker
Status: NEW → ASSIGNED
Blocks: 1892084
No longer blocks: 1829758

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.

Pushed by dbaker@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c9bfe7c044aa
Implement |setCodecPreferences| in RTCRtpTransceiver;r=bwc,jib,webidl,smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/46235 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
Upstream PR merged by moz-wptsync-bot
Upstream PR merged by moz-wptsync-bot

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)

relnote-firefox: --- → ?
Keywords: dev-doc-needed

Added to the Fx128 relnotes.

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

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: