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

From the spec perspective, adding text that says that if the [proximity to the viewport](https://drafts.csswg.org/css-contain/#proximity-to-the-viewport) is [not determined](https://drafts.csswg.org/css-contain/#not-determined), then don't fire the event. This ensures that we don't fire the event eagerly, since the proximity should be determined at the next update the rendering loop

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


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

Received on Monday, 22 January 2024 16:28:30 UTC