- From: steimelchrome <notifications@github.com>
- Date: Wed, 14 Feb 2024 10:50:13 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 14 February 2024 18:50:21 UTC
> Thanks for clarifying @domenic, I understand the reasoning more clearly now. > > A clarifying question: Where does this restriction of one PiP window per top-level traversable come from? Is it to prevent abuse and improve the end-user experience? Or is it an underlying platform limitation? It's not an underlying platform limitation. It's more to prevent abuse and improve the end-user experience. In fact, in Chrome we currently only allow one video OR document picture-in-picture window total across all tabs, though that is stricter than the spec dictates. There's concern that multiple always-on-top windows can quickly become unwieldy -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/798#issuecomment-1944405628 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/798/1944405628@github.com>
Received on Wednesday, 14 February 2024 18:50:21 UTC