- From: Chris Needham via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Mar 2024 17:56:46 +0000
- To: public-secondscreen@w3.org
So now I'm looking at **local playback state** as a better place to mention this, and it made me wonder about the interaction between Remote Playback and Picture in Picture. I don't think it's enough to simply say that PiP playback is considered local: * What should happen to the PiP state if the user initiates remote playback while a PiP window is open? * What should happen if the user tries to [request PiP](https://w3c.github.io/picture-in-picture/#request-pip) while the [remote playback state](https://w3c.github.io/remote-playback/#the-state-attribute) is anything other than **disconnected**. What do implementations currently do in these scenarios? -- GitHub Notification of comment by chrisn Please view or discuss this issue at https://github.com/w3c/remote-playback/pull/153#issuecomment-2015628907 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 March 2024 17:56:47 UTC