- From: Frank <notifications@github.com>
- Date: Thu, 20 Apr 2023 14:08:34 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 20 April 2023 21:08:39 UTC
> Can you elaborate on how this concern has been addressed? In the response to this question I'm reading from @liberato-at-chromium "However, I don't believe that Document PiP makes the situation any worse." We're trying to push spec developers to "leave the web better than you found it." [...] So I think we'd like to understand how Document picture-in-picture makes things _better_ for end users on this front. Document PiP makes the web better because we've seen a lot of (legitimate, not abusive) demand for always-on-top arbitrary content. My comments earlier were just trying to say that we aren't introducing a new vector for abuse in the process of providing those improvements, because it's not more abusable that what's already there. I might be able to make the case that it's actually less so. For example, the site can't move or resize a document pip window via scripting. However, I don't think those differences are a reason we'd do any of this. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/798#issuecomment-1516950943 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/798/1516950943@github.com>
Received on Thursday, 20 April 2023 21:08:39 UTC