- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Mar 2025 16:04:27 +0000
- To: public-css-archive@w3.org
OK, discussed this at internal sync. Proposal is to perform initial content visibility state if needed as we're iterating over the element tree when capturing the new state. So when we walk the tree, and run into an element with `content-visibility: auto` whose [proximity to the viewport](https://drafts.csswg.org/css-contain/#proximity-to-the-viewport) is not determined and it is not [relevant to the user](https://drafts.csswg.org/css-contain/#relevant-to-the-user), we determine [proximity to the viewport](https://drafts.csswg.org/css-contain/#proximity-to-the-viewport) for that element. From a web-observable perspective it's roughly equivalent to what was proposed before, but it's clearer here that this is specifically for making sure this state is determined before checking for view-transition elgibility. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10773#issuecomment-2701389923 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 March 2025 16:04:28 UTC