Re: [csswg-drafts] [css-contain-3] Proposal: Add an event to fire when content-visibility: auto state changes (#7384)

Hey, thanks for your comments and for taking the time to discuss this outside of this thread.

The conclusion we seemed to have reached is that we can proceed with speccing this event, but we should add normative developer guidance in the spec (and mdn) to avoid cases that break the semantic meaning of elements affected by c-v auto. IOW, since currently the content is semantically relevant regardless of whether it's skipped by c-v auto, this event should not be used to break that (e.g. by stopping all updates indefinitely, although deprioritizing the updates is a reasonable use case).

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


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

Received on Thursday, 28 July 2022 14:28:33 UTC