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
There currently exists a Web API for putting an HTMLVideoElement into a
Picture-in-Picture window (HTMLVideoElement.requestPictureInPicture()). This
limits a website's ability to provide a custom picture-in-picture experience
(PiP). We want to expand upon that functionality by giving websites the ability
to open a picture-in-picture (i.e., always-on-top) window with a blank document
that can be populated with arbitrary HTMLElements instead of only a single HTMLVideoElement.
This new window will be much like a blank same-origin window opened via the
existing window.open() API, with some differences:
The PiP window will float on top of other windows.
The PiP window will never outlive the opening window.
The website cannot set the position of the PiP window.
The PiP window cannot be navigated (any window.history or window.location
calls that change to a new document will close the PiP window).
Zoom Team votes one for this feature as it's definitely a nice-to-have improvement to allow application owner to implement more advanced user experiences based on DOM.
Introduction
There currently exists a Web API for putting an
HTMLVideoElement
into aPicture-in-Picture window (
HTMLVideoElement.requestPictureInPicture()
). Thislimits a website's ability to provide a custom picture-in-picture experience
(PiP). We want to expand upon that functionality by giving websites the ability
to open a picture-in-picture (i.e., always-on-top) window with a blank document
that can be populated with arbitrary
HTMLElement
s instead of only a singleHTMLVideoElement
.This new window will be much like a blank same-origin window opened via the
existing
window.open()
API, with some differences:window.history
orwindow.location
calls that change to a new document will close the PiP window).
Read the complete Explainer.
Feedback
I welcome feedback in this thread, but encourage you to file bugs against the Explainer.
The text was updated successfully, but these errors were encountered: