feat: add browser.IS_CHROMECAST_RECEIVER and class name for CSS targeting on a Chromecast receiver where Video.js is used #8703
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.
Description
Some people may want to use Video.js as part of their Chromecast receiver application - particularly for UI customization. This PR builds on #8676 by adding feature detection for a Chromecast receiver context.
I did not test this on a cast device as I do not own one!
Specific Changes proposed
browser.IS_CHROMECAST_RECEIVER
booleanvjs-device-chromecast-receiver
class name for players running on a Chromecast receiver deviceRequirements Checklist