Re: [csswg-drafts] [css-display-4] Is reading-order-items the best name for this property? (#9921)

The CSS Working Group just discussed `[css-display-4] Is reading-order-items the best name for this property?`, and agreed to the following:

* `RESOLVED: rename the property to reading-flow`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> rachelandrew: So this is about the naming<br>
&lt;bramus> … current name is reading-order-items. Reason is that there was a prev proposal with a reading-order property on the parent. we now dont have a child property and kept the reading-order-items nmae<br>
&lt;bramus> … devs suggested to use reading-order<br>
&lt;bramus> … other suggestion is reading-flow but less keen on that (so are devs) as it has name overlap with the flow properties from flex<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> +1 to reading-order<br>
&lt;astearns> q+<br>
&lt;bramus> … suggestion to use reading-order here, and maybe use reading-order-index if we bring back a property for child items<br>
&lt;iank_> i like reading-order<br>
&lt;bramus> fantasai: so reason for reading-order was to match with order and more specifically that and make visual-order longhands of the order property<br>
&lt;bramus> … we made a mistake by not naming order propert not visual-order. confuses people<br>
&lt;astearns> q-<br>
&lt;bramus> … if we want to introduce reading-order and its not parallel with order property blocks us from fixing later<br>
&lt;bramus> … it would mean the two props ar enot on the same level<br>
&lt;lwarlow> big +1 to what Elika is saying<br>
&lt;TabAtkins> that makes sense as an argument against reading-order<br>
&lt;bramus> astearns: so you are suggesting on the name for the container prop to be what?<br>
&lt;TabAtkins> then I transfer my vote to reading-flow<br>
&lt;bramus> fantasai: anything other than reading-order<br>
&lt;bramus> … reading-flow is more consistent<br>
&lt;bramus> … with flex and stuff<br>
&lt;TabAtkins> q+<br>
&lt;astearns> ack dbaron<br>
&lt;bramus> dbaron: I think order wasnt best name in the first place either. we had precedent for reordring things with numbers. propably too late to go back to index-naming<br>
&lt;astearns> ack TabAtkins<br>
&lt;bramus> fantasai: we discussed that, for some reason other people won<br>
&lt;bramus> TabAtkins: elika’s argumetn against reading-order makes sense, speficially wrt order prop. reading-flow works. got a few flow props that do this in an analogous way<br>
&lt;bramus> rachelandrew: i’d be happy with that<br>
&lt;bramus> … i get the argument<br>
&lt;florian> q+<br>
&lt;bramus> … better than reading-order-items<br>
&lt;astearns> ack florian<br>
&lt;bramus> florian: i am convinced by elika’s arg<br>
&lt;TabAtkins> Plus it doesn't *really* follow the *-items pattern anyway (which is just "set this value on my children, because it's not actually an inherited property"<br>
&lt;bramus> … as for reading-flow: seems ok. doesnt strike me as amazing but maybe that’s good as it might force people to think before adding it<br>
&lt;bramus> lwarlow: reading-order-type could be an alternative to avoid flow<br>
&lt;bramus> … agree with everything elika said<br>
&lt;bramus> … the thing doesnt take a number<br>
&lt;bramus> astearns: any opinions on reading-order-type?<br>
&lt;TabAtkins> straw poll?<br>
&lt;dbaron> I still prefer reading-flow over reading-order-type<br>
&lt;bramus> fantasai: reading-flow has my preference<br>
&lt;bramus> … I like parellelism with grid-auto-flow and flex-flow<br>
&lt;bramus> … it does something similar to those<br>
&lt;florian> reading-flow seems fine<br>
&lt;kbabbitt> +1 to reading-flow<br>
&lt;bramus> astearns: I think we can resolve on reading-flow unless anyone else makes an argument for reading-order-type<br>
&lt;bramus> … proposed resolution to remame the property to reading-flow<br>
&lt;lwarlow> +1<br>
&lt;bramus> … objections?<br>
&lt;bramus> RESOLVED: rename the property to reading-flow<br>
</details>


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


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

Received on Thursday, 13 June 2024 08:22:35 UTC