1329847 - Implement RTCDegradationPreference related functions

Status: RESOLVED FIXED

(Core :: WebRTC: Networking, task, P3)

Description

[detour]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

When bandwidth gets worse, it is needed to disable video resolution change sometimes. There is related definition here https://www.w3.org/TR/webrtc/#idl-def-rtcdegradationpreference for this requirement. Would you please consider implement it?

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

Not sure if we should make this a low p1.  p2 for now

Comment 2

[Bulk Bug Changes for mreavy's org]

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

Comment 4

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

The spec is now located here https://w3c.github.io/mst-content-hint/#dom-rtcrtpsendparameters-degradationpreference

This would let apps configure how a WebRTC call should degrade in the face of bandwidth constriction. For instance, an app might want to drop resolution for camera video, but not for a screen presentation, where it might choose to drop frame rate instead. Another app might choose differently.

Comment 5

[Dan Baker[:dbaker]]

Attachment: Bug 1329847 - Implement RTCDegradationPreference API.;r=jib!,bwc!,pehrsons!

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2ff799b75977
Implement RTCDegradationPreference API.;r=jib,bwc,pehrsons,webidl,smaug

Comment 7

[Dan Baker[:dbaker]]

The current MDN shows this as being deprecated/deleted. This is incorrect and needs to be updated, the feature was moved under content-hints https://w3c.github.io/mst-content-hint/#degradation-preference-when-encoding.

Comment 8

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/2ff799b75977

Comment 9

[Dianna Smith [:diannaS]]

:dbaker is this something you want to mention in the 138 release notes as well? If so, feel free to nominate it.

Comment 10

[Dan Baker[:dbaker]]

Release Note Request (optional, but appreciated)
[Why is this notable]: Applications can now set their preferred degradation method to be utilized when encoding the configured framerate and resolution cannot be maintained.
[Affects Firefox for Android]: Yes
[Suggested wording]: The RTCDegradationPreference method allows applications to override the browser's default degradation behavior with one of the following values: "maintain-framerate", "maintain-resolution", or "balanced".
[Links (documentation, blog post, etc)]: https://w3c.github.io/mst-content-hint/#degradation-preference-when-encoding

Comment 11

[Dianna Smith [:diannaS]]

Added to the 138 nightly release notes and on track to be in the final release notes.

Comment 12

[Hamish Willee]

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