Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Provide a clear definition of when a UA should display controls in a PiP window #119
The spec today states the following with respect to a UA displaying controls that map to MediaSession actions:
It makes sense for a play/pause control to be continually shown in a PiP window, however, for the remaining actions (seekbackward, seekforward, previoustrack, nexttrack, and skipad), it seems like there would be value in specifying that UAs which choose to display controls should either hide or disable UI elements that map to actions that do not have a
It will be hard to add web platform tests for those but I'd be happy to reconsider defining whether controls should be displayed in the PiP window in this spec.
Note that in Chrome for instance, we have special rules for the play/pause button. If video is a mediastream or has infinite duration, we don't show it by default unless MediaSession actions are set for "play" and "pause".