Skip to content

Conversation

@wbamberg
Copy link
Collaborator

@wbamberg wbamberg commented Feb 6, 2026

As far as we can tell, the Media Capabilities API page and guide make some claims about the API that are unsupported. This PR removes them.

@wbamberg wbamberg requested a review from a team as a code owner February 6, 2026 23:34
@wbamberg wbamberg requested review from chrisdavidmills and removed request for a team February 6, 2026 23:34
@github-actions github-actions bot added Content:WebAPI Web API docs size/s [PR only] 6-50 LoC changed labels Feb 6, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

Preview URLs (2 pages)

(comment last updated: 2026-02-07 18:34:40)

@wbamberg wbamberg changed the title Remove some incorrect statements Remove some incorrect statements about the Media Capabilities API Feb 6, 2026
Copy link
Collaborator

@hamishwillee hamishwillee left a comment

Choose a reason for hiding this comment

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

Excellent thank you.

I was going to comment that there is quite a big caveat on "if playback should be smooth and power efficient." - the method relies on statistics being gathered, so when you first try it the method really only allows checking for codec type (all supported configs report as performant and smooth until after the connection has run for a bit).

But this is corrections, so out of scope.

@hamishwillee hamishwillee merged commit 962e1a5 into mdn:main Feb 8, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:WebAPI Web API docs size/s [PR only] 6-50 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants