- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 18:03:24 +0000
- To: public-css-archive@w3.org
> I guess it works, but seems a bit weird to have a one-off exception Not exactly one-off. `content-visibility` is subtle this way. There's other cases like `getComputedStyle` which force computing style for an element outside the rendering loop. In this case we don't need to force computing style, since VT spec already says that elements which aren't relevant to the user can be ignored. But we need to know which elements are relevant to the user. That said, happy to hear if you have any other suggestions. Early on we considered running the [capture the new state](https://drafts.csswg.org/css-view-transitions-1/#capture-new-state-algorithm) algorithm within update the rendering loop that would have avoided it. But we needed to give authors a script hook to set up web animations targeting pseudo-elements after this step. And more script hooks in the later stages of update the rendering become a pain to maintain. There's already a loop there which has to run resize observer and content visibility state tracking multiple times until it settles. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10773#issuecomment-2307565243 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 18:03:25 UTC