Chrome 144 adds RTCDegradationPreference maintain-framerate-and-resolution

[chrisdavidmills]

… value

Summary

Chrome 144 adds support for the maintain-framerate-and-resolution value of the RTCDegradationPreference dictionary, which is used in the options object of the RTCRtpSender.setParameters() method, and available in the return value of the RTCRtpSender.getParameters() method.

See https://chromestatus.com/feature/5156290162720768 for the release details.

This PR adds a sub-data point to each method's data structure for this new value.

Test results and supporting details

Related issues

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[caugner]

I can see how it could be useful if we captured this level of detail (what values a property in the returned object can take), but ultimately I don't think it makes sense for the getter.

[chrisdavidmills]

OK, fair enough. I've removed this sub-data point from the getter.

[caugner]

Does this mean the other three values are not supported?

• "maintain-framerate"
• "maintain-resolution"
• "balanced"

If some of these are also supported (possibly in an earlier version), we should add them as well.

[chrisdavidmills]

The other values have been supported since the property was first implemented. In my experience, people tend to assume that API data where you only list the property and not all of its values separately means that all the values are supported, not none of the values are supported. So we tend to only list separate sub-points for values that started to be supported later.