- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2024 17:30:55 +0000
- To: public-css-archive@w3.org
Reading the above descriptions, I'm a little confused by what "taking `writing-mode` into account" means. Are there any cases where using `writing-mode` can cause items to be read backwards from the "logical" order that was used to place them (assuming they weren't placed explicitly with `grid-row`, `grid-column`, or `grid-area`)? (It seems like the only thing in the existing proposal that allows reading in the reverse of the "logical" order is the combination of `reading-order-items: flex-visual` with `flex-direction`: `row-reverse` | `column-reverse` or `flex-wrap: wrap-reverse`, and I don't see anything in the alternative proposal that allows that.) On a separate topic, it feels like part of @bradkemper's position is making the argument that the default value is wrong, and the default should be visual order rather than DOM order. That seems like an even bigger change, but it also feels inconsistent to accept that argument without also changing the default. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9923#issuecomment-2161279461 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 June 2024 17:30:55 UTC