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

Hi folks,
  
We (@plinss @matatk and I) discussed this again during a breakout today.
  
Overall, we see *why* the current `window.open()` doesn’t work for what this API is trying to do, however it appears that *all* of these differences are things that would be useful for `window.open()` as well:
  
- An async API to allow gating behind a permissions prompt
- Feature detection for individual parameters
- Allowing up to one window per top-level traversible
- Ability to create "always on top" windows
- ...
  
We understand that improving `window.open()` is a substantial undertaking, however from an architectural point of view, we cannot justify creating a parallel, more narrowly scoped API for the sole reason of avoiding that work. Instead, we encourage people to work on the [existing effort](https://github.com/whatwg/html/issues/7485) to modernize `window.open()` and ensure it covers these use cases as well.
  
The video-specific use cases appear to be covered already by `video.pictureInPicture()` so designing this as a more general API seems appropriate. It is unfortunate that not every existing platform can implement this API, but it is clear that there are use cases that go beyond video, so we think that as long as feature detection is possible and has good ergonomics, this may be worth doing. 

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

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