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
As of Chromium v116, the documentPictureInPicture.requestWindow() method was added, which allows to embed not just the video but any element in the PiP window, this could be useful for subtitles because they stay behind when the PiP button is pressed.
I understand this is a client-side change so it will be possible to accomplish from channel custom JS, but it could still be the default behavior of the video player.
It seems like this feature isn't available in Firefox; I usually try to constrain core features to things that are standardized and work across all major browsers to reduce user confusion and troubleshooting burden.
Could you explain a little more about the problem you were trying to solve by requesting this feature? There may be an alternative way to support the use case that doesn't rely on nonstandard features.
I am among the people who spearheaded/promoted the existence of the dPIP work. You can rest assured that custom subtitle support in PIPs will be coming once Mozilla is onboard with the feature too.
calzone: they want a solution for this. When you activate PIP/video popout mode, layered elements like canvas generated subtitles do not come along for the ride. I agree we should wait for Firefox to support this feature as well before including it in core.
As of Chromium v116, the
documentPictureInPicture.requestWindow()
method was added, which allows to embed not just the video but any element in the PiP window, this could be useful for subtitles because they stay behind when the PiP button is pressed.I understand this is a client-side change so it will be possible to accomplish from channel custom JS, but it could still be the default behavior of the video player.
Additional info:
VideoJS demo by Chrome devs (source code)
Official documentation
WICG Explainer
The text was updated successfully, but these errors were encountered: