Add <audio> and <video> features #1337
Conversation
The overall status matches caniuse with these exceptions: - Chrome 4 is the earliest possible version in caniuse, so it cannot match BCD's claim of Chrome 3. - Partial support due to parts of the API being unavailable or not working isn't reproduced. This is clear from the statuses of the individual BCD keys instead. HTMLMediaElement is made part of <video> only for now. Everything is Baseline high except for volume and playbackRate.
github-actions
bot
added
the
feature definition
| # baseline: false | ||
| # support: | ||
| # chrome: "3" | ||
| # chrome_android: "18" | ||
| # edge: "12" | ||
| # firefox: "3.5" | ||
| # firefox_android: "4" | ||
| # safari: "3.1" | ||
| - api.HTMLMediaElement.volume | ||
|
|
||
| # baseline: false | ||
| # support: | ||
| # safari: "3.1" | ||
| # safari_ios: "3" | ||
| - api.HTMLMediaElement.playbackRate |
There was a problem hiding this comment.
FWIW, both of these have dodgy-looking data. Someday someone might come along and fix it 😄
There was a problem hiding this comment.
playbackRate is about only Safari supporting a negative playback rate. The spec does allow for throwing an exception "if the given value is not supported by the user agent" but doesn't require any specific playback rates to be supported.
volume is about it not doing anything on iOS.
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
|
A summary of a side-channel chat between me and @ddbeck. The reason to avoid "plays" in the description here would be the precedent that we need to pick a verb for every element, leading to things like " |
The overall status matches caniuse with these exceptions:
match BCD's claim of Chrome 3.
working isn't reproduced. This is clear from the statuses of the
individual BCD keys instead.
HTMLMediaElement is made part of
Everything is Baseline high except for volume and playbackRate.