Re: [csswg-drafts] [css-view-transitions-2] Elements with content-visibility in new Document (#10773)

The CSS Working Group just discussed `[css-view-transitions-2] Elements with content-visibility in new Document`, and agreed to the following:

* `RESOLVED: compute missing content-visibility information as we iterate the tree while capturing`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> noamr: this is a lifecycle issue with view transitions<br>
&lt;kbabbitt> ... don't capture v-t if it's not relevant to user<br>
&lt;kbabbitt> ... away from viewport, content-visibility auto<br>
&lt;kbabbitt> .... issue with cross document v-t<br>
&lt;kbabbitt> ... might not know yet if an element is close to viewport or not<br>
&lt;kbabbitt> ... also if element were added between starting v-t and activating it<br>
&lt;kbabbitt> ... original idea was to play around with order in rendering lifecycle but that caused issues<br>
&lt;kbabbitt> ... proposal on issue now is that when we go through the tree of elements to see what needs to be captured<br>
&lt;kbabbitt> ... if we didn't compute content-visibility for an element, then we do<br>
&lt;kbabbitt> ... v-t algo iterates over all elements anyway<br>
&lt;kbabbitt> ... to find capture<br>
&lt;kbabbitt> ... so if it finds an element that's new and we don't know if it's captured<br>
&lt;kbabbitt> ... compute what we need for it at that point<br>
&lt;kbabbitt> noamr: wouldn't change behavior in chromium, would probably fix a bug in firefox<br>
&lt;kbabbitt> Rossen9: any feedback?<br>
&lt;kbabbitt> Rossen9: all for fixing bugs, not hearing anyone from gecko side express concerns<br>
&lt;kbabbitt> noamr: Proposed: compute missing content-visibility information as we iterate the tree while capturing<br>
&lt;kbabbitt> Rossen9: objections?<br>
&lt;kbabbitt> RESOLVED: compute missing content-visibility information as we iterate the tree while capturing<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10773#issuecomment-3079426767 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 16 July 2025 16:46:04 UTC