Re: [w3ctag/design-reviews] Early design review: Document Picture-in-Picture (Issue #798)

> * Yes, in this model if the main frame is navigated (even to the same origin) the PiP window is killed (similar to the existing requestPictureInPicture() API for HTMLVideoElement)
> * N/A
> * That is left up to the user agent (similiar to the existing requestPictureInPicture() API for HTMLVideoElement). In Chrome, we will only allow one PiP window to exist at a time. I know other browsers do something different for HTMLVideoElement and therefore may do something different for this as well.
> * Yes. I originally had it on navigator, but was told that it wasn't a good place for the API. I don't have strong feelings about API name or placement personally

@steimelchrome have you updated the explainer to clarify these issues? (And by the way, thanks @slightlyoff!) 
  
From our review in today's TAG breakout, this looks like a generally useful feature.

A few other questions:

* what is the planned route for standardizaion for this? Right now it just lists WICG.
* we noted that while the explainer is well written, it doesn't start with user needs as we've been encouraging. Can you add some material documenting the use cases from a user's perspective?
* is there any relationship with Popover #743 - considering these are both to do with layering of content
* we discussed a potential issue around accessibility... for example if there are subtitles in the PiP "window" ensuring those can be picked up by assistive technology appropriately. What other accessibility considerations have you discussed?
* we're slightly concerned with the proposed mitigation to the [spoofing issue](https://wicg.github.io/document-picture-in-picture/#spoofing) - although it's good that this consideration is called out. Can you strengthen this wording maybe with an example?
* we'd like to encourage you to use normative language in the security and privacy considerations sections, as you develop those further
* has there been any feedback from other browsers?  Have you opened up issues in Mozilla or Webkit standards positions?
* how would this feature work with multiple screens? Would it be up to implementations to decide which screen the PIP window shows up in? It seems like it would be useful to 

Also just noting: we're going to bring more CSS expertise to bear on this review so expect some further questions.
  
Thanks!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/798#issuecomment-1457785020
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/798/1457785020@github.com>