You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on spec edits for reading order. @bradkemper proposes that the property be named reading-order or reading-flow not reading-order-items.
Summary of discussion so far:
The name reading-order-items (on the flex or grid container to indicate reading order behavior of direct children) was used as we initially had reading-order as a property for the children (with a value of auto or <integer>.
The current edits do not include a reading-order property as it was resolved in 8589 that we did not need it.
We do intend to leave the possibility of bringing back a property for the children in future, so any naming should keep sensible possibilities for that in mind.
Brad's argument for reading-flow is that it makes sure there is no link with the order property, which could be confusing.
Question for the group is should we keep reading-order-items as the name for the property on the parent, drop the suffix and use reading-order or move completely away from mention of order and use reading-flow?
The text was updated successfully, but these errors were encountered:
As a CSS author, the part of the property name that confused me was the -items suffix. reading-order is a more understandable alternative. I also vote for reading-order over reading-flow because we usually discuss "DOM order" (not "DOM flow") versus "Visual display order" (not "visual display flow"), and the visual order is changed using the order property, so "reading order" makes sense and is easier to relate back to the former two concepts.
Working on spec edits for reading order. @bradkemper proposes that the property be named
reading-order
orreading-flow
notreading-order-items
.Summary of discussion so far:
reading-order-items
(on the flex or grid container to indicate reading order behavior of direct children) was used as we initially hadreading-order
as a property for the children (with a value ofauto
or<integer>
.reading-order
property as it was resolved in 8589 that we did not need it.reading-flow
is that it makes sure there is no link with theorder
property, which could be confusing.Question for the group is should we keep
reading-order-items
as the name for the property on the parent, drop the suffix and usereading-order
or move completely away from mention of order and usereading-flow
?The text was updated successfully, but these errors were encountered: