You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers would like to control more of the audio/video user experience. The :playing, :paused, :seeking, :buffering, :stalled, :muted, and :volume-locked CSS pseudo-classes match <audio> and <video> elements based on their state.
Thank you for proposing Media element pseudo-classes for inclusion in Interop 2025.
We wanted to let you know that this proposal was not selected to be part of Interop this year.
On behalf of the entire Interop team, thank you for submitting this proposal for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2025.
Description
Developers would like to control more of the audio/video user experience. The
:playing
,:paused
,:seeking
,:buffering
,:stalled
,:muted
, and:volume-locked
CSS pseudo-classes match<audio>
and<video>
elements based on their state.Specification
https://www.w3.org/TR/selectors-4/#resource-pseudos
WPT
css/selectors/media/media-loading-state.html
css/selectors/media/media-playback-state.html
css/selectors/media/sound-state.html
Additional Signals
Could be used by sites like Vimeo, YouTube, etc
The text was updated successfully, but these errors were encountered: