Skip to content

Chrome 144 RTCDegradationPreference maintain-framerate-and-resolution… #28898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chrisdavidmills wants to merge 3 commits into
base: main
Choose a base branch
from
+32 −0
Open

Chrome 144 RTCDegradationPreference maintain-framerate-and-resolution… #28898

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4082485
Chrome 144 RTCDegradationPreference maintain-framerate-and-resolution…
chrisdavidmills Jan 23, 2026
519608c
Merge branch 'main' into rtcdegradationpreference-maintain-framerate-…
chrisdavidmills Jan 24, 2026
1521286
remove getter data
chrisdavidmills Jan 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions api/RTCRtpSender.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -627,6 +627,38 @@
"standard_track": true,
"deprecated": false
}
},
"maintain-framerate-and-resolution_value": {
Copy link
Contributor

@caugner caugner Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

@chrisdavidmills chrisdavidmills Jan 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

"__compat": {
"description": "`maintain-framerate-and-resolution` value",
"spec_url": "https://w3c.github.io/mst-content-hint/#dom-rtcdegradationpreference-maintain-framerate-and-resolution",
"support": {
"chrome": {
"version_added": "144"
},
"chrome_android": "mirror",
"edge": "mirror",
"firefox": {
"version_added": false
},
"firefox_android": "mirror",
"oculus": "mirror",
"opera": "mirror",
"opera_android": "mirror",
"safari": {
"version_added": false
},
"safari_ios": "mirror",
"samsunginternet_android": "mirror",
"webview_android": "mirror",
"webview_ios": "mirror"
},
"status": {
"experimental": true,
"standard_track": true,
"deprecated": false
}
}
}
},
"parameters_encodings_parameter": {
Expand Down