- From: Gideon Caspi via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Apr 2023 08:41:11 +0000
- To: public-css-archive@w3.org
Having read the [Chrome blog write-up](https://developer.chrome.com/blog/reading-order/), this seems like a great idea that admittedly I haven't hit too much, but have wondered about its implications when I have. My initial thoughts are that it would be useful for the defaults to solve most use cases so that the reading order follows the layout, rather than having to remember "when I change the rendering order of the source I also need to apply a few more new rules". The `reading-order` and `focus-order` rules would then be useful for intentionally following the CSS-defined layout if that's desired. This stems from a feeling that this should be handled automatically with available manual interventions for rare cases that would want to follow the source order in visually modified layouts, in line with; > We could also consider making the default ordering visual in cases such as grid masonry layout, or auto-flow: dense where reordering is almost inevitable. -- GitHub Notification of comment by GideonCaspi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7387#issuecomment-1515948149 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 April 2023 08:41:13 UTC