- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Apr 2025 19:28:33 +0000
- To: public-css-archive@w3.org
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> <fantasai> kizu: Right now you have to say `inside` or `outside` always. Maybe we want to just default to `inside`.<br> <fantasai> kizu: one common case is doing something like `anchor(inside --foo 0)`<br> <fantasai> kizu: Just a very small thing<br> <iank_> q+<br> <fantasai> TabAtkins: no strong opinion. Agree inside is the best default<br> <astearns> ack iank_<br> <fantasai> iank_: I would be hesitant to doing this. For anchor-size() 99% of the time you wnat same axis<br> <fantasai> iank_: but here, I don't know what the percentage breakdown but it's not anything like that<br> <fantasai> iank_: it'll be split evenly<br> <fantasai> iank_: so for that reason I don't think we should omit this<br> <TabAtkins> yeah actually i retract my "best default:<br> <fantasai> kizu: It will be split if you mention just one side<br> <TabAtkins> `inset` it's the best default, `left` outside is the best default<br> <fantasai> kizu: but if you use the shorthands, only 'inside' make sense<br> <TabAtkins> fantasai: i think for shorthands, inside is 100% the right default<br> <TabAtkins> fantasai: for individual sides, it is more often that you'd use outside<br> <TabAtkins> fantasai: but yeah it's probabyl on the 60/40 side<br> <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> <fantasai> kizu: I think this was also before position-area, which makes this a bit easier<br> <fantasai> kizu: So not strong issue for me<br> <TabAtkins> yeah, just `position-area:left` means you rarely need to mention anchor() anyway<br> <fantasai> astearns: so propose to close no chnage<br> <fantasai> astearns: objections?<br> <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