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

Hi @steimelchrome,

First of all we know we're late getting back to you on this. Thank you for bearing with us. 

We appreciate the addition of normative language around spoofing. We remain concerned about the lack of multi-stakeholder support - particularly the lack of support from other browsers - unlike picture in picture itself which enjoys strong support across engines. We're also concerned that this feature could be used to enable surprising and disruptive advertising experiences. We also remain concerned about the browser chrome around this picture-in-picture window. E.g. the documentation presumes there will be a close button but this is highly dependent on platform.

In terms of API design, we did see a lot of commonalities between this functionality and an "always on top" option in `window.open()`. Integrating it in `window.open()` would also fix a lot of issues around it (guaranteed prominent window chrome, guaranteed close button, existing ways to interact with said windows, naming, namespacing etc) and it also reduces the new API surface that authors need to learn. We do [see](https://github.com/WICG/document-picture-in-picture#since-this-is-pretty-close-to-windowopen-why-not-just-add-an-alwaysontop-flag-to-windowopen) that this was considered as an alternative, but rejected due to lack of feature detectibility for `window.open()` options and some functional differences (never outliving the opener). There are [discussions](https://github.com/whatwg/html/issues/7485) around creating a new method that fixes the various issues of `window.open()`, it may be a good idea to collaborate with the folks working on this effort. The functional differences between this and `window.open()` may be useful more broadly too, never outliving the opener certainly would be!

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

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