Document partners interested in the API

[beaufortfrancois]

It would be nice to list partners who are interested in the API and document their specific use cases (if any) in the https://github.com/WICG/document-picture-in-picture/blob/main/README.md.

[austinh]

Hello! Software Engineer from Spotify here. We intend to use document Picture in Picture API for playing podcast and music video video content - as well as as a mini media player for songs/audiobooks with visual content . The current picture in picture API does not allow customization of the UI. We hope to have our own player interface - and have it change based on the visual format - for example song visuals might have a different UI than video content, etc .

We’ve experimented with using canvas and the current PiP API but ran into issues with DRM. Having a document with customizable elements would be the ideal developer experience

[chrisn]

BBC is interested in using this API for video with custom player controls and caption rendering for accessibility to be able to apply our branding and UX to the picture in picture window as we can with our regular in-page video player.

[mmarzullotv]

@beaufortfrancois

We are also interested on allowing live stream using Picture-in-Picture mode along with React components but doesn't seem to be very supported.

We were trying to create a specific Layout UI for PiP only. The idea is to be able to inject fully React customizable components along with their respective styling and business logic. Right now, if you try to append a button that has an event handler bound to it from the parent document to pip children window, the handler will be lost.

Is this API working only with plain javascript for now? If not and actually can work with React, do you mind sharing a snippet achieving this?

Thanks in adv!

[sahiltalwar88]

Hi there! Moving here from the above thread as suggested by @chrisn.

My company would love a more generalized, non-video-specific PiP as well; our use case is guiding a user through a workflow that exists across apps (or sites).

The idea is that the PiP window can float above the content with:

• directions explaining what to do
• navigation buttons (e.g. "next" and "back" to go back and forth between the various steps of the workflow, along with a cancel button)
  help icon / tooltip / etc

What are the next steps to push to include this in the next version of the standard?

[HolgerJeromin]

We (making a web-based machine visualization) are thinking about moving an existing popup onscreen keyboard into this API.
So the users can move our keyboard without having the page content covered.

[beaufortfrancois]

FYI The Document Picture-in-Picture is shipping in Chrome 116 (https://chromestatus.com/feature/5755179560337408)