Document PiP adds a new API to open an always-on-top window that can be populated with arbitrary HTMLElements. This is an expansion upon the existing HTMLVideoElement API that only allows for an HTMLVideoElement to be put into a PiP window. This allows web developers to provide a better PiP experience to users.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
N/A since we are not enabling this API on Android
We want to make sure the API is ergonomic/powerful enough to enable websites to provide the improved picture-in-picture experiences they've wanted to create (improved vs the existing video picture-in-picture API). We'll look at developer feedback for issues/limitations that we hadn't considered. We'll look at the usage of the CSS copying feature to see if it's actually useful and worth pursuing.
N/A
None
The new methods and properties proposed in this spec will show up in autocomplete functionality (e.g. window.documentPictureInPicture). The enter event will support event listener breakpoints in the "Picture-in-Picture" category.
At least initially, we're not supporting Android since the Android APIs don't easily support always-on-top windows with arbitrary interaction
OriginTrial desktop last | 115 |
OriginTrial desktop first | 111 |
Note on the WebKit signal: They do have some concerns listed on the GitHub issue but no official position
On Monday, January 9, 2023 at 11:15:30 AM UTC-8 Tommy Steimel wrote:
Explainer
https://github.com/WICG/document-picture-in-picture/blob/main/README.mdSpecification
https://wicg.github.io/document-picture-in-pictureSummary
Document PiP adds a new API to open an always-on-top window that can be populated with arbitrary HTMLElements. This is an expansion upon the existing HTMLVideoElement API that only allows for an HTMLVideoElement to be put into a PiP window. This allows web developers to provide a better PiP experience to users.
Blink component
Blink>Media>PictureInPictureTAG review
https://github.com/w3ctag/design-reviews/issues/798
TAG review status
PendingRisks
Interoperability and Compatibility
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/670)
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/03e97552-6e27-4c24-8a79-7b2f7f43e28en%40chromium.org.