- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Apr 2024 21:50:32 +0000
- To: public-css-archive@w3.org
I think this issue can be closed. Masonry presents no new problems that aren't already present with Grid's arbitrary reordering capability, so any solutions that we come up with for *either* will fix *both*. And we have indeed come up with such a solution, via [`reading-order-items`](https://drafts.csswg.org/css-display-4/#reading-order-items). Tho also, `reading-order-items` won't even be necessary by default - if you're just auto-flowing things in a Masonry, you'll get an approximation to the standard reading order anyway, and that's exactly what the property would do. `reading-order-items` will just fix cases where you're either using `order` to change up the layout order, or explicitly placing some items in tracks. (Note that the example in the OP showing a confusing order won't happen by default; it requires "over" to have been explicitly placed there, and possibly "the lazy" too. The default placement will instead make the last row `[over][dog][the lazy]`, and since `[dog]` is somewhat lower than the other two, it's reasonable for the eyes to scan it after `[over]` and `[the lazy]` and get the expected reading order.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5675#issuecomment-2080163667 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 April 2024 21:50:34 UTC