Re: [csswg-drafts] [css-env-1] Specify viewport environment variable property propagation into subframes (#10506)

The CSS Working Group just discussed `[css-env-1] Specify viewport environment variable property propagation into subframes`, and agreed to the following:

* `RESOLVED: top frame and any fullscreen subframes get insets set, but not otherwise`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> flackr: we have safr area inset in environment variables thjat allow authors to avoid placing content in areas not guaranteed to be visibile<br>
&lt;kbabbitt> ...example around notch<br>
&lt;kbabbitt> ...we have a difference i whether those variables are set in subframes<br>
&lt;kbabbitt> ...on Safari it has the same values<br>
&lt;kbabbitt> ...in my demo you can see content in inner frame having same insets even though inner frame is nowhere near edge of screen<br>
&lt;kbabbitt> ...in Chrome we pass these insets through only when frame is fullscreen<br>
&lt;kbabbitt> ...we also set insets on main frame<br>
&lt;kbabbitt> ...proposal is that for inner frames by default we don't pass through insets<br>
&lt;kbabbitt> ...because it's up to the author to position so it avoids that area<br>
&lt;kbabbitt> ...unless frame has been made fullscreen<br>
&lt;kbabbitt> ...any frame that's been made fullscreen gets those insets<br>
&lt;TabAtkins> +1 from me<br>
&lt;fantasai> sgtm<br>
&lt;kbabbitt> astearns: questions?<br>
&lt;kbabbitt> astearns: concerns?<br>
&lt;kbabbitt> Proposed: insets are not passed through to inner frames by default<br>
&lt;kbabbitt> Proposed: top frame and any fullscreen subframes get insets set, but not otherwise<br>
&lt;kbabbitt> astearns: objections?<br>
&lt;kbabbitt> RESOLVED: top frame and any fullscreen subframes get insets set, but not otherwise<br>
</details>


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


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

Received on Thursday, 26 September 2024 19:07:42 UTC