Re: [csswg-drafts] [css-contain-2]: Should the first `contentvisibilityautostatechange` event be fired without knowing if the element is close to the viewport (#9803)

The CSS Working Group just discussed ``[css-contain-2]: Should the first `contentvisibilityautostatechange` event be fired without knowing if the element is close to the viewport``, and agreed to the following:

* `RESOLVED: if a c-v:auto element is skipping its contents but has not yet determined its visiblity, don't fire the contentvisibilityautostatechange event until you do know the visibility`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> vmpstr: we have an even tthat fires when content-visibility:auto state changes (form skipped to not skipped, or vice versa)<br>
&lt;TabAtkins> vmpstr: question, what to do if we haven't determined visibility for the element yet<br>
&lt;TabAtkins> vmpstr: can happen if we add the c-v:auto then force rendering<br>
&lt;TabAtkins> vmpstr: visibility is done at IO timing, so not done yet<br>
&lt;TabAtkins> vmpstr: naively we'd fire an event that says "it's skipped" then at IO time we fire another saying "it's visible", two events in rapid succession<br>
&lt;TabAtkins> vmpstr: filer of the issue suggests we just don't fire the event until we've actually had a chance to determine the visibility<br>
&lt;TabAtkins> +1, makes sense to me<br>
&lt;TabAtkins> vmpstr: one extra - "unless there's something else making the element relevant to the user", then we already know it's relevant and fire it immeidately<br>
&lt;TabAtkins> vmpstr: so if the element is skipping its ocntents but we haven't determined its visibility yet, don't fire the event<br>
&lt;chrishtr> +1 to the resolution<br>
&lt;TabAtkins> RESOLVED: if a c-v:auto element is skipping its contents but has not yet determined its visiblity, don't fire the contentvisibilityautostatechange event until you do know the visibility<br>
</details>


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


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

Received on Thursday, 7 March 2024 00:57:11 UTC