- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jan 2025 23:56:02 +0000
- To: public-css-archive@w3.org
Given the combined discussion in this issue and its [whatwg counterpart](https://github.com/whatwg/html/issues/10533), the proposal we decided on is option 2: Make a reading flow item with display: contents a focus scope owner. This approach allows us to respect the accessibility tree for all cases and scope tabindex ordering within it. This might result in some tab/visual mismatch, but those should be edge cases. This option respects the resolutions from the CSSWG that: * reading-flow does not affect whether an element is focusable as it only re-order focusable elements * display:contents focusable element occurs immediately before its first child in visual order Since all these resolutions are about focus scope owner and how to find the next focusable element, this issue can be closed and conversation can continue in whatwg where the algorithm will be written. -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9230#issuecomment-2576444521 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 January 2025 23:56:04 UTC