Re: [csswg-drafts] [css-anchor-position] Nailing down the position-try-options "flip" behavior (#10049)

The CSS Working Group just discussed `[css-anchor-position] Nailing down the position-try-options "flip" behavior`.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> https://drafts.csswg.org/css-anchor-position-1/#swap-due-to-a-try-tactic<br>
&lt;emeyer> TabAtkins: Elika brought this up to bring it to WG attention<br>
&lt;emeyer> …As far as I know, this all is good and it works as expected in Chrome<br>
&lt;emeyer> …Happy to tweak as necessary if anything is wrong<br>
&lt;astearns> ack fantasai<br>
&lt;emeyer> fantasai: Do we flip the safe area sides on the end function<br>
&lt;emeyer> …If you stick this into a `left` property, does it get flipped to the `right` property?<br>
&lt;fantasai> s/end/env()/<br>
&lt;emeyer> TabAtkins: Great question; right now, we already substitute variables and I think the answer is we substitute pre-flipping<br>
&lt;emeyer> …So what ever it resolves to on the left, it resolves to that and is flipped to the right<br>
&lt;emeyer> …This is what you want for vars, but for env() specifically, we could do something different if we need to<br>
&lt;emeyer> …I'm not certain what the ideal behavior would be, whether we want to do that before or after<br>
&lt;emeyer> …In general, env() is used fairly little, so we should be able to experiement and change if need be<br>
&lt;emeyer> astearns: Any other comments?<br>
&lt;emeyer> fantasai: I note that the margin properties are only mentioned in an example<br>
&lt;emeyer> TabAtkins: They don't need to be mentioned otherwise because it refers to the list of position-try properties and margins are on the list<br>
&lt;emeyer> astearns: Woiuld you like a resolution from the WG?<br>
&lt;emeyer> fantasai: Could or not, but I wanted to bring to the WG's attention that this is happening<br>
&lt;emeyer> astearns: So please take a look at this, and fantasai please look at where the swapping should happen<br>
&lt;emeyer> fantasai: I think it should happen before, but I'm not sure<br>
&lt;emeyer> TabAtkins: We'll open another issue for that<br>
&lt;fantasai> s/not sure/not sure it's implementable/<br>
</details>


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


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

Received on Tuesday, 11 June 2024 08:38:31 UTC