Display and content-visibility animations

[josepharhar]

こんにちは TAG-さん!

I'm requesting a TAG review of Display and content-visibility animations.

Support specifying display and content-visibility in animations. This support allows for developers to create exit animations after which the element automatically becomes display: none or content-visibility: hidden without needing to write any javascript to handle that switch after the animation is finished. This allows exit animations for elements to be added purely in CSS.

• Explainer¹ (minimally containing user needs and example code): [css-display] Why is display listed as not animatable instead of animation type: discrete? w3c/csswg-drafts#6429 (comment)
• Specification URL: https://drafts.csswg.org/css-display-4/#display-animation
• Tests:
  • https://wpt.fyi/results/css/css-display/animations/display-interpolation.tentative.html
  • https://wpt.fyi/results/web-animations/animation-model/animation-types/display.tentative.html
• User research: none
• Security and Privacy self-review²: none, I believe this animations feature has no security/privacy implications.
• GitHub repo (if you prefer feedback filed there): none
• Primary contacts (and their relationship to the specification):
  • Joey Arhar @josepharhar Google
  • Robert Flack @flackr Google
• Organization(s)/project(s) driving the specification: Google
• Key pieces of existing multi-stakeholder review or discussion of this specification: [css-display] Why is display listed as not animatable instead of animation type: discrete? w3c/csswg-drafts#6429
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5154958272364544

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: We are trying to ship this in Chrome 114 which branches on April 20th and goes to stable on May 30th
• The group where the work on this specification is currently being done: CSSWG
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): 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 (please delete all but the desired option):

💬 leave review feedback as a comment in this issue and @-notify [github usernames]

[josepharhar]

This feature is now handled by #829