- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Jul 2024 21:11:23 +0000
- To: public-css-archive@w3.org
I have done more research and thinking about this open question. We came up with two main options on how to handle it. * Option 1: Visit all items of a reading flow container in their layout order, followed by all `display: contents` *descendants* of the container. * Option 2: Make a reading flow item with display: contents a focus scope owner. This means visiting all the *direct* children of the reading flow container together and create more focus scopes as necessary. We also recommend visiting all `display: contents` elements after the sorted reading flow items. We wrote out the HTML spec changes necessary and illustrated the approach with examples at https://github.com/whatwg/html/issues/10533. @rachelandrew has also posted a [blog post](https://developer.chrome.com/blog/reading-flow-display-contents?hl=en) detailing the problem. We recommend developers to give us feedback here or on the whatwg issue :) -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9230#issuecomment-2261469723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 July 2024 21:11:24 UTC