- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 23:38:45 +0000
- To: public-css-archive@w3.org
To summarize, the questions are: 1. Should a display: contents (with tabindex=0) be considered a reading order item? 2. Should a display: contents’ children be considered reading order items? 3. HTML standard expect to traverse within focus scopes, where a focus scope owner can be a shadow host, a slot, a document, etc. This conflicts with reading order, where we are depending on a flattened tree traversal and display: contents/slots don’t matter. Potential resolutions: 1. Make display: contents elements not reading order focusable. 2. Make display: contents children not reading order focusable (fallback to using source order). 3. Tell users to avoid display: contents for reading order. 4. Or other suggestions and considerations? -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9230#issuecomment-2164072674 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 June 2024 23:38:46 UTC