- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2023 09:59:15 +0000
- To: public-css-archive@w3.org
I had a look through the initial examples of this that developers had raised (under [examples from the community n the initial issue](https://github.com/w3c/csswg-drafts/issues/7387)). The things people are wanting to do seem solved by the proposed solution. [Tweaks, for example to form layout, when source is not modifiable](https://twitter.com/Spinal83/status/1531600852611366912). This isn't an ideal use, and advice would be to reorder the HTML where possible, but people are going to do this sort of thing. However this could be solved by changing the layout in grid then asking the reading order to follow that order. [Different layouts for different screen sizes](https://twitter.com/VincentTunru/status/1531586369109348352). This is the use case that comes up most often, and is solved by the current suggestion, assuming the grid layout is adjusted in the media/container query and the `reading-order-items` property applied at the same time. [Deliberate reordering, where you want the source and display order to be different](https://twitter.com/aardrian/status/1531610793023787008) and [this tweet](https://twitter.com/hovhaDovah/status/1531681075562520579) still works as now, as you just don't use `reading-order-items` in that circumstance. I can't think of, nor have I encountered from the community, an instance where we need `<reading-order: <integer>`. It feels as if this simpler approach solves the use cases I'm trying to solve for. It also doesn't block us moving forward with the `<integer>` case in future if such a need arises. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8589#issuecomment-1721007301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 September 2023 09:59:16 UTC