ContentVisibilityAutoStateChanged event

[vmpstr]

Request for position on an emerging web specification: ContentVisibilityAutoStateChanged event

Information about the spec

• Spec Title: CSS Contain: Content Visibility
• Spec URL: This will be an amendment to https://drafts.csswg.org/css-contain-2/
• Issue Tracker (if not the repository's issue tracker): https://github.com/w3c/csswg-drafts/issues
• Explainer (if not README.md in the repository): https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md

Design reviews and vendor positions

• TAG Design Review: ContentVisibilityAutoStateChanged event w3ctag/design-reviews#756
• Mozilla standards-positions issue: ContentVisibilityAutoStateChanged event mozilla/standards-positions#664

Anything else we need to know

CSSWG discussion: w3c/csswg-drafts#7384 (comment)

[hober]

The relevant spec text is https://drafts.csswg.org/css-contain-2/#content-visibility-auto-state-change

[annevk]

So this event is intentionally not synchronized with rendering updates? Although it does seem like the task queueing should happen from the "update the rendering" algorithm given what appears to trigger it.

cc @smfr @nt1m

[nt1m]

@rwlbuis @cathiechen

[annevk]

Discussing this with colleagues it seems like this should be "position: support". If anyone disagrees, please say so within a week. Thanks!

[nt1m]

This is fine to us, and we actually landed the implementation in WebKit.