[w3ctag/design-reviews] ContentVisibilityAutoStateChanged event (Issue #756)

Hello TAG!

I'm requesting a TAG review of ContentVisibilityAutoStateChanged event.

This proposal is to add an event that would fire on a `content-visibility: auto`
element when the rendering state of the element changes due to any of the
attributes that make the element [relevant to the
user](https://www.w3.org/TR/css-contain-2/#relevant-to-the-user).

  - Explainer¹ (minimally containing user needs and example code): [explainer](https://github.com/vmpstr/web-proposals/blob/main/explainers/cv-auto-event.md)
  - Specification URL: This will be an amendment to [css-contain](https://drafts.csswg.org/css-contain-2/) spec. I will update the issue once the spec text is available.
  - Security and Privacy self-review²: [self-review](https://github.com/vmpstr/web-proposals/blob/main/security-assessments/cv-auto-event.md)
  - Primary contacts (and their relationship to the specification):
      - Vladimir Levin (@vmpstr, Google)
      - Tab Atkins (@tabatkins, Google)
  - Organization(s)/project(s) driving the specification: Google
  - Key pieces of existing multi-stakeholder review or discussion of this specification: [CSSWG discussion](https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1176847043)
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5179553291436032


Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: None
  - The group where the work on this specification is currently being done: CSSWG
  - Major unresolved issues with or opposition to this specification: None
  - This work is being funded by: Google

We'd prefer the TAG provide feedback as:

  💬 leave review feedback as a **comment in this issue** and @-notify @vmpstr


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/756

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/756@github.com>

Received on Monday, 11 July 2022 16:49:58 UTC