- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Feb 2025 21:55:00 +0000
- To: public-css-archive@w3.org
Given resolution at https://github.com/w3c/csswg-drafts/issues/11208#issuecomment-2625850559, maybe we need to consider how property reading-order affect reading-flow's initial value. What do we think of supporting the following values for `reading-flow`: * flex-visual, flex-flow, grid-order, grid-rows, grid-columns: As described in spec. * none: Follow the order of elements in the DOM order, with no reading-flow container and does not affect the focus order at all. * normal: default Then, normal will be interpreted as follow: 1. If it is a grid container and any of its items has `reading-order`; then use `grid-order`. 2. Else if it is a flex container and any of its items has `reading-order`; then use `flex-flow`. 3. Else if it has `grid-auto-flow: dense` or `grid-auto-flow: dense row`; use `grid-rows`. 4. Else if it has `grid-auto-flow: dense column`; use `grid-columns`. 5. Else; use `none`. 1-2 would help to handle reading-oder while 3-4 are to solve the current issue. -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11396#issuecomment-2638106785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 February 2025 21:55:01 UTC