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

> According to [2], whether it is [close to the viewport](https://drafts.csswg.org/css-contain/#close-to-the-viewport) could not be determined in at least one frame. Should the first `contentvisibilityautostatechange` event be fired without this value?

I'm not sure I follow. The proximity to the viewport is determined in one frame. The effect of that on the relevant state may be deferred to the next frame per item 3 and 4 of https://drafts.csswg.org/css-contain/#cv-notes

Perhaps the `contentvisibilityautostatechange` event should fire when the `content-visibility: auto` element starts or stops `skipping its contents` (instead of being `relevant to the user`). This would essentially only change the timing of the event, and it would align to the proposal here to not fire it too eagerly

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


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

Received on Wednesday, 17 January 2024 15:49:35 UTC