-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
[HTMLMediaElement] Add a controlsList/controlslist attribute #6715
base: main
Are you sure you want to change the base?
Conversation
@domenic Please review |
So it isn't lost with the new PR, WebKit's expressed opposition to this feature hasn't changed. |
For reference, here's the related blink-dev thread: https://groups.google.com/a/chromium.org/g/blink-dev/c/u9jsiarDEOg |
Did you miss my comment about WebKit's opposition to this feature? |
Argh! I did miss editing my blink-dev draft. Thanks for the ping @eric-carlson |
Pinging this thread because my information says this is shipping in 93. Should this be in the spec for real? |
How about being able to add custom buttons to the list? say like a quality picker for example. |
This option is currently only supported by chromium-based browsers (Chrome, Edge, Brave etc.). Firefox and Safari do _not_ support this option, since they both don't offer a download button at all (see whatwg/html#6715)
As discussed in #2426 (comment), this PR overseeds #2426 and adds a
controlslist
content attribute reflected by a DOMTokenList attribute namedcontrolsList
to theHTMLMediaElement
for<audio>
and<video>
tags.It specifies the following keywords:
nodownload
,nofullscreen
,noplaybackrate
(new in this PR) andnoremoteplayback
.💥 Error: Wattsi server error 💥
PR Preview failed to build. (Last tried on May 25, 2021, 9:13 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.