Re: [csswg-drafts] Upstream Document Picture-in-Picture (#13707)

The CSS Working Group just discussed `Upstream Document Picture-in-Picture`, and agreed to the following:

* `RESOLVED: accept upstreaming the feature, Emilio to do edits`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> emilio: gecko is implementing document pip, currently in WICG<br>
&lt;TabAtkins> emilio: it monkey patches a bunch of specs, would like to upstream it<br>
&lt;TabAtkins> emilio: main css-releavnt patches are CSSOM View<br>
&lt;TabAtkins> emilio: So q is, are there any concerns?<br>
&lt;TabAtkins> TabAtkins: so long as it's being implemented i'm happy to have them upstreamed<br>
&lt;TabAtkins> emilio: Chrome does, Firefox is doing it, unsure webkit<br>
&lt;TabAtkins> florian: how big is it?<br>
&lt;TabAtkins> emilio: not big, two special cases<br>
&lt;TabAtkins> emilio: requires user activation for resizeTo() and for moving...<br>
&lt;TabAtkins> emilio: doesn't allow<br>
&lt;astearns> https://wicg.github.io/document-picture-in-picture/#positioning<br>
&lt;TabAtkins> emilio: goal is just to prevent the pip window from growing to obscure the whole screen<br>
&lt;TabAtkins> emilio: i'll do the edits<br>
&lt;TabAtkins> florian: sounds good to me<br>
&lt;emilio> https://wicg.github.io/document-picture-in-picture/#resizing-the-pip-window / https://wicg.github.io/document-picture-in-picture/#moving-the-pip-window<br>
&lt;TabAtkins> proposed: accept upstreaming the feature, Emilio to do edits<br>
&lt;TabAtkins> RESOLVED: accept upstreaming the feature, Emilio to do edits<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13707#issuecomment-4180802021 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 2 April 2026 22:24:03 UTC