Re: [csswg-drafts] [css-anchor-position] could anchor()'s side argument be optional? (#10408)

The CSS Working Group just discussed `[css-anchor-position] could anchor()'s side argument be optional?`, and agreed to the following:

* `RESOLVED: Close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> kizu: Right now you have to say `inside` or `outside` always. Maybe we want to just default to `inside`.<br>
&lt;fantasai> kizu: one common case is doing something like `anchor(inside --foo 0)`<br>
&lt;fantasai> kizu: Just a very small thing<br>
&lt;iank_> q+<br>
&lt;fantasai> TabAtkins: no strong opinion. Agree inside is the best default<br>
&lt;astearns> ack iank_<br>
&lt;fantasai> iank_: I would be hesitant to doing this. For anchor-size() 99% of the time you wnat same axis<br>
&lt;fantasai> iank_: but here, I don't know what the percentage breakdown but it's not anything like that<br>
&lt;fantasai> iank_: it'll be split evenly<br>
&lt;fantasai> iank_: so for that reason I don't think we should omit this<br>
&lt;TabAtkins> yeah actually i retract my "best default:<br>
&lt;fantasai> kizu: It will be split if you mention just one side<br>
&lt;TabAtkins> `inset` it's the best default, `left` outside is the best default<br>
&lt;fantasai> kizu: but if you use the shorthands, only 'inside' make sense<br>
&lt;TabAtkins> fantasai: i think for shorthands, inside is 100% the right default<br>
&lt;TabAtkins> fantasai: for individual sides, it is more often that you'd use outside<br>
&lt;TabAtkins> fantasai: but yeah it's probabyl on the 60/40 side<br>
&lt;fantasai> TabAtkins: I'm weakly against because the weakness of the defaulting argument here. Wouldn't oppose if strong arguments, but prefer to skip<br>
&lt;fantasai> kizu: I think this was also before position-area, which makes this a bit easier<br>
&lt;fantasai> kizu: So not strong issue for me<br>
&lt;TabAtkins> yeah, just `position-area:left` means you rarely need to mention anchor() anyway<br>
&lt;fantasai> astearns: so propose to close no chnage<br>
&lt;fantasai> astearns: objections?<br>
&lt;fantasai> RESOLVED: Close no change<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10408#issuecomment-2776733836 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 19:28:34 UTC