- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 13 May 2026 15:57:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-animations-2] Add the `animation-end-delay` property``, and agreed to the following: * `RESOLVED: Introduce animation-delay-start and animation-delay-end as longhands of animation-delay, making the animation-delay-end value optional and defaulting to zero (not duplicating start)` <details><summary>The full IRC log of that discussion</summary> <fantasai> ydaniv: This is about exposing the end delay to the declarative syntax<br> <fantasai> ydaniv: It's already a property that we have on the imperative API<br> <fantasai> ydaniv: Proposal is to have animation-delay become a shorthand of animation-delay-start and animation-delay-end<br> <bramus> q+<br> <fantasai> ydaniv: both are time values, defualt to zero<br> <fantasai> ydaniv: and the end delay is optional<br> <fantasai> fantasai: And it defaults to zero, not matching the start value<br> <astearns> ack bramus<br> <bramus> q-<br> <fantasai> bramus: That was going to be my question :)<br> <fantasai> astearns: Proposed to accept the proposal, and clarify that animation-delay-end defaults to zero.<br> <fantasai> PROPOSED: Introduce animation-delay-start and animation-delay-end as longhands of animation-delay, making the animation-delay-end value optional and defaulting to zero (not duplicating start)<br> <fantasai> RESOLVED: Introduce animation-delay-start and animation-delay-end as longhands of animation-delay, making the animation-delay-end value optional and defaulting to zero (not duplicating start)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13863#issuecomment-4442858056 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 May 2026 15:57:19 UTC