- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Aug 2023 21:36:31 +0000
- To: public-css-archive@w3.org
> 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'm not sure quite what you mean by this. In the flex/grid cases, DOM order is already completely lost. Other than its incidental effects on how elements get automatically ordered, there's nothing left there. Visual order inherently and necessarily is post-`order`. In the "DOM order, but let order take effect as well" example I was asking about, it would also be an intentional opt-in. > 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.) This is the `reading-order: <integer>` case that we're explicitly discarding for now, right? (Tho the "DOM order, but pay attention to `order`" would also allow this if the call-outs were explicitly positioned, as they could then use `order` without actually affecting their position, just their paint layering.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8589#issuecomment-1690677694 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 21:36:33 UTC