Re: [csswg-drafts] [css-display-4] Do we need `reading-order: <integer>` or should `reading-order: auto` be allowable in all grid or flex layouts? (#8589)

Some comments:

- Grid has a `grid-auto-flow`, should there be a keyword that simply matches it?
- I'm not sure having the multiple-keyword syntax is helpful, maybe these can just be hyphenated?
- Relatedly, maybe `reading-flow` is a reasonable name, since it relates to `flex-flow` and `grid-auto-flow`?
- I'm hesitant to have `order` overriding DOM in the reading order unless the author very explicitly requests it, because the main purpose of `order` is to diverge logical and spatial order. So I don't want to do that without the author opting in intentionally.
- I can also see use cases for wanting a reading order that pulls some items out of the background coordinate-based flow (e.g. in a grid) and makes them first or last in the reading order while leaving them in the middle of the visual flow. Imagine, for example, a grid of small cards with a few pulled out and enlarged 2x2: a visual navigator would perceive those 2x2 cards first, and then the rest of them, so you might want to match the reading order to that. (Or you might not, depends what you're doing.)


-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8589#issuecomment-1690330738 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 August 2023 17:09:43 UTC