Re: [csswg-drafts] [css-anchor-position-1] Can we clarify the `inset-area` syntax? It can be confusing to read and reason about. (#9862)

The CSS Working Group just discussed ``[css-anchor-position-1] Can we clarify the `inset-area` syntax? It can be confusing to read and reason about.``, and agreed to the following:

* `RESOLVED: switching center-* keywords to span-* and all to span-all`

<details><summary>The full IRC log of that discussion</summary>
&lt;keithamus> TabAtkins: changing inset area syntax was discussed at f2f. People didn't like keywords. fantasai and I are weakly in favour of switching to span-left or span-start to indicate center and the other direction<br>
&lt;TabAtkins> `bottom center-left`<br>
&lt;fantasai> used to be `bottom / center left`<br>
&lt;keithamus> TabAtkins: Right now if you wanted to express &lt;select>, it fills the center and right<br>
&lt;emilio> Select element behavior is actually different across platforms :')<br>
&lt;keithamus> TabAtkins: Proposal is more like a background syntax, we use center-* properties to indicate 2 column or 2 row.l<br>
&lt;TabAtkins> `bottom center` vs `bottom-center`<br>
&lt;dbaron> (fantasai's and Tab's irc comments above should be reordered, I think)<br>
&lt;fantasai> maybe we need keywords for platform behaviors...<br>
&lt;keithamus> TabAtkins: These were two extremely different areas being selected<br>
&lt;TabAtkins> `bottom span-left`<br>
&lt;keithamus> TabAtkins: So all center-* words are now span-*<br>
&lt;keithamus> TabAtkins: bottom row, span from center to left columns.<br>
&lt;keithamus> TabAtkins: in terms of number-pad in a 3x3 grid, cells 1 and 2<br>
&lt;keithamus> TabAtkins: unless anyone has a great opinion, I suggest we go with these as a different suggestion. Center being unclear, space or dash when saying out loud, and still is reasonably readable<br>
&lt;keithamus> astearns: I agree this is an improvement<br>
&lt;keithamus> dbaron: it seems less clear to me in the syntax that it's occupying two grid spaces.<br>
&lt;keithamus> TabAtkins: it's spanning, so by definition it covers multiple spaces<br>
&lt;fantasai> keithamus: At GH we have an implementation that uses compass directions<br>
&lt;TabAtkins> keithamus: at github we have an impl that uses compass direction<br>
&lt;TabAtkins> also, for example, `span-bottom span-left` covers 4 cells (4512 on numpad), and can't be written with compasses<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/9862#issuecomment-1924919417<br>
&lt;keithamus> fantasai: for background position we have very analgous syntax. We can't use compass directions because we have several different coordinate systems to worry about. Start-x, start-y, x and y, and block-start, inline-start, etc. The syntax... there is a lot of keywords.<br>
&lt;keithamus> fantasai: this is a bunch of stuff that can be expressed in background position<br>
&lt;astearns> ack dbaron<br>
&lt;keithamus> dbaron: what's the current syntax for spanning all 3?<br>
&lt;keithamus> TabAtkins: all<br>
&lt;keithamus> TabAtkins: I'd be comfortable switching to span-all.<br>
&lt;keithamus> astearns: Are you uncomfortable with this dbaron?<br>
&lt;miriam> +1 span-all and span-(direction)<br>
&lt;keithamus> dbaron: I'm okay, I just would prefer something clearer<br>
&lt;keithamus> fantasai: I'd like to resolve on something so we can put a stake in the ground and publish a spec<br>
&lt;fantasai> s/I'd like/Can keep the issue open, but I'd like/<br>
&lt;keithamus> PROPOSED RESOLUTION: switching center-* keywords to span-* and all to span-all<br>
&lt;keithamus> RESOLVED: switching center-* keywords to span-* and all to span-all<br>
</details>


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


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

Received on Wednesday, 6 March 2024 17:48:55 UTC