Extend PiP standard to non-video content types

[sahiltalwar88]

My company and I have come up with what we believe is a very legitimate use case for a more generalized, non-video-specific PiP: 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

We even have a demo of this that I'd be happy to walk someone through, if it would help. What are the next steps to push to include this in the next version of the standard?

[chrisn]

Thanks for raising this. You may be interested in the Document PiP proposal. There's a GitHub issue in their repo where you can show your interest.