- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Nov 2022 18:50:35 +0000
- To: public-css-archive@w3.org
> I guess we're talking about doing something different than that for view transitions Yes. getBoundingClientRect will force style/layout for a node which is "not relevant to the user" and is in locked state. One difference between this and view transitions is that the forced style/layout only happens if the developer queries this info from script. With view transitions if we take the same pattern we'll have to force style resolution for the entire DOM even if there is no node with a `view-transition-name` under a `content-visibility: auto` node. There also won't be a way for the developer to indicate that no such node exists and the browser can avoid the style walk without an explicit property (like contain: view-transition-name). That's why I'm more inclined to skip discovering view-transition-names under a DOM node if its not relevant to the user. And letting authors use `content-visibility: visible` if they want such names to be discovered deterministically. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7874#issuecomment-1307679425 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 November 2022 18:50:37 UTC