Contact email
Summary
-internal-media-controls-cast-button will no longer be exposed to web contents. That means that the remote playback icon from the native controls will no longer be customizable via CSS.
Motivation
-internal-media-controls-cast-button should never have been exposed to web contents in the first place. Furthermore, we now have an API for websites to reimplement the native cast button feature (using Remote Playback API) so a website that wants a custom cast button can use custom controls.
Compatibility And Interoperability Risk
The selector has been available for as long as Chrome Android supports video flinging (couple
of years). However, breakage would only be superficial and make websites controls look like regular native controls.
Alternative implementation suggestion for web developers
Using custom controls with Remote Playback API to implement the cast button is the recommended way to work around this deprecation.
Usage information from UseCounter
Usage is very low (0.0044%) but still existent:
https://www.chromestatus.com/metrics/feature/timeline/popularity/1063
We will look at the data when M59 is around the corner but unless things change significantly, we consider the usage low enough to be safe to remove at the moment.
OWP launch tracking bug
Entry on the feature dashboard
https://www.chromestatus.com/feature/5734009183141888
Requesting approval to remove too?
Yes. We would like to remove the selector support in M59.
lgtm1
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.