feat(controlsList): passing through Chrome's controlsList attribute #40
Conversation
This file contains 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
Google Chrome allows an attribute 'controlsList', which allows you to blacklist certain controls, like the download button. This change passes the attribute through so that it can be used with ReactAudioPlayer. https://googlechrome.github.io/samples/media/controlslist.html
|
Thanks for following up on this! Works for me locally and the PR looks perfect. I'll go ahead and merge this and then make a new release shortly. |
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.
Google Chrome allows an attribute 'controlsList', which allows you to
blacklist certain controls, like the download button. This change passes
the attribute through so that it can be used with ReactAudioPlayer.
https://googlechrome.github.io/samples/media/controlslist.html
Originally filed in #35, but I closed that one since React didn't support the attribute.
However, support was added in 15.6.2, so this should be good now.