- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jul 2023 16:31:18 +0000
- To: public-css-archive@w3.org
We're adding this to the agenda to see if we can get agreement on the simplified approach discussed in https://github.com/w3c/csswg-drafts/issues/8589 I wrote this up as a blog post, which has examples of the two possible ways an author would invoke this ordering. 1. [Randomized layouts](https://developer.chrome.com/blog/reading-order/#following-randomized-layouts-with-reading-order-auto) (such as dense packing and masonry) 2. [Non randomized layouts](https://developer.chrome.com/blog/reading-order/#following-non-randomized-layouts-with-reading-order-items) where the author is moving items away from the DOM order intentionally and wants the reading order to follow. So the proposal is to keep `reading-order: auto` on the grid items of randomized methods, and to add a `reading-order-items` property for the grid or flex container, which is used in the non-randomized cases, allowing the author to explain their intent for the reading order. We simplify by removing `reading-order: <integer>`, however this approach wouldn't prevent us from going down that line in the future if needed. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7387#issuecomment-1640556638 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 July 2023 16:31:20 UTC