Move two getCapabilities() methods out of media capabilities
#3270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These aren't part of the same API. They're defined here: https://w3c.github.io/mediacapture-main/#dom-inputdeviceinfo-getcapabilities https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack-getcapabilities Removing the compute_from here to match the feature description makes the Baseline year change from 2020 to 20222, but this seems OK.
github-actions
bot
added
the
feature definition
ddbeck
approved these changes
Aug 26, 2025
ddbeck
changed the title
getCapabilities() methods out of media capabilities
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These aren't part of the same API. They're defined here:
https://w3c.github.io/mediacapture-main/#dom-inputdeviceinfo-getcapabilities
https://w3c.github.io/mediacapture-main/#dom-mediastreamtrack-getcapabilities
Removing the compute_from here to match the feature description makes
the Baseline year change from 2020 to 20222, but this seems OK.