- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2023 15:42:40 +0000
- To: public-css-archive@w3.org
The other part of the discussion on Monday was the idea that there are multiple ways one could want to auto-order certain layouts. A flexbox might want to go in flex order (source order + 'order'), or in logical order (start from the startmost flex line, and the startmost item in it, then proceed, so 'flex-direction' and 'flex-wrap' also affect things). A grid might want to be read in column-major order or row-major order. Etc. It sounds like *that's* something that would be indicated on the container itself. So I think my proposal is that we should keep the current spec as written, but add a property on the container (`reading-order-order`, clearly) that controls how we assign the ordering to `reading-order: auto` children. Give it an initial value that only has an effect on randomized layouts, and then we can extend it with specific-layout keywords for those other cases as we come up with them. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8589#issuecomment-1470276382 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 March 2023 15:42:42 UTC