- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 23:03:32 +0000
- To: public-css-archive@w3.org
Given the summary comment above, I propose we resolve to answer “no” to 1a. For 1b, I propose that the reading flow focus navigation should be opted-in explicitly via a separate CSS property. Why: we should only encourage using reading flow when the visual order is different from the DOM order, such as in flex and grid containers. This is in line with the CSS order property, which also only works in flex or grid containers. If it is really necessary to allow reading-order to take effect without specifying reading-flow flex-*/grid-* values, then we should at least make it very explicit by using a new keyword like `source`. This would help the author be aware that the focus order changed. Authors often copy/paste code around and if they set reading-order on an item that isn’t even a flex/grid item, then making it opt into reading flow doesn’t make sense and would be unexpected. -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11208#issuecomment-2686404260 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 23:03:33 UTC