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

@steimelchrome 
> Re: modernized window.open(): Domenic gave some input on this in the intent to ship: [groups.google.com/a/chromium.org/g/blink-dev/c/JTPl7fM64Lc](https://groups.google.com/a/chromium.org/g/blink-dev/c/JTPl7fM64Lc)

Thanks, I found @domenic’s [comment](https://groups.google.com/a/chromium.org/g/blink-dev/c/JTPl7fM64Lc/m/OfBZRdjEAAAJ), though it took a little digging. Presumably this is the main part:
> There is some TAG feedback that seems to wish this was part of window.open() or some other more-general API, but I think that advice is not correct, and the current API design is good, due to the singleton-per-top-level-traversable nature of a document PiP window. In my opinion this makes the window.documentPictureInPicture entrypoint, with its requestWindow(), window, and onenter properties, a good API for the use case.

We'd love if you or @domenic could elaborate on this, as we're a bit unclear on the argument being made (e.g. what is singleton-per-top-level-traversable-nature?).

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

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