- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Apr 2025 17:15:51 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-anchor-position] flip should also flip safe-area-inset values`, and agreed to the following: * `RESOLVED: env(safe-area-inset-*) flip also` <details><summary>The full IRC log of that discussion</summary> <fantasai> scribe+<br> <fantasai> fantasai: position-try flipping should also flip the safe-area-insets<br> <fantasai> TabAtkins: If you have left: env(safe-area-inset-left) and you flip that to become a top value, you almost certainly want to use the safe-area-inset-top instead of the left.<br> <fantasai> TabAtkins: That seemed obvious, so I edited it in.<br> <TabAtkins> commit is here https://github.com/w3c/csswg-drafts/commit/e143edf116418e86e6c940061515d856a70a8d2d<br> <fantasai> astearns: Does this only happen for top-level values that are the appropriate env() function<br> <fantasai> astearns: or any component of the value that might happen to be referenced<br> <fantasai> TabAtkins: the env() function itself will flip if the property flips<br> <fantasai> astearns: if it's wrapped in complicated calc()<br> <fantasai> TabAtkins: they all filip<br> <fantasai> s/filip/flip/<br> <fantasai> astearns: any other questions?<br> <fantasai> PROPOSED: env(safe-area-inset-*) flip also<br> <fantasai> RESOLVED: env(safe-area-inset-*) flip also<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10422#issuecomment-2776455378 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 April 2025 17:15:52 UTC