Title: CSS Animations Module Level 2
Status: ED
Work Status: Exploring
Shortname: css-animations
Level: 2
Group: csswg
ED: https://drafts.csswg.org/css-animations-2/
TR: https://www.w3.org/TR/css-animations-2/
Previous Version: https://www.w3.org/TR/2023/WD-css-animations-2-20230602/
Editor: L. David Baron, Google https://www.google.com/, https://dbaron.org/, w3cid 15393
Editor: Brian Birtles, Invited Expert, brian@birchill.co.jp, w3cid 43194
!Issues List: https://github.com/w3c/csswg-drafts/labels/css-animations-2
Abstract: This CSS module describes a way for authors to animate the values of CSS properties over time, using keyframes. The behavior of these keyframe animations can be controlled by specifying their duration, number of repeats, and repeating behavior.
Ignored Vars: auto-rewind
urlPrefix: https://dom.spec.whatwg.org/; type: dfn; spec: dom
    text: event target

Delta specification

This is a delta specification, meaning that it currently contains only the differences from CSS Animations Level 1 [[!CSS3-ANIMATIONS]]. Once the Level 1 specification is closer to complete, it will be merged with the additions here into a complete level 2 specification.

# Animations # {#animations} Changes to any of the animation properties defined in this specification cause the corresponding {{CSSAnimation}} object and its associated objects to be updated according to the correspondence between these properties and Web Animations concepts defined in [[#keyframes]]. However, if the author modifies the animation using the Web Animations programming interface, the changes from the programming interface take precedence as follows: * After a successful call to {{KeyframeEffect/setKeyframes()}} on the {{KeyframeEffect}} associated with a {{CSSAnimation}}, any subsequent change to matching ''@keyframes'' rules or the resolved value of the 'animation-timing-function' property for the target element will not be reflected in that animation. However, if the last matching ''@keyframes'' rule is removed the animation must still be canceled. * After a successful call to {{AnimationEffect/updateTiming()}} on the {{KeyframeEffect}} associated with a {{CSSAnimation}}, for each property included in the {{AnimationEffect/updateTiming(timing)/timing}} parameter, any subsequent change to a corresponding animation property will not be reflected in that animation. For example, calling cssAnimation.effect.updateTiming({ duration: 1000 }) would cause subsequent changes to 'animation-duration' to be ignored whilst changes to 'animation-delay' would still be reflected in the {{KeyframeEffect}}'s timing. * After a successful call to {{Animation/play()}} or {{Animation/pause()}} on a {{CSSAnimation}}, any subsequent change to the 'animation-play-state' will no longer cause the {{CSSAnimation}} to be played or paused as defined in [[#animation-play-state]]. * After a successful call to {{Animation/reverse()}} on a {{CSSAnimation}} or after successfully setting the {{Animation/startTime}} on a {{CSSAnimation}}, if, as a result of that call the [=play state=] of the {{CSSAnimation}} changes to or from the [=play state/paused=] play state, any subsequent change to the 'animation-play-state' will no longer cause the {{CSSAnimation}} to be played or paused as defined in [[#animation-play-state]]. The requirement for a change to or from the [=play state/paused=] state ensures that even after calling {{Animation/reverse()}} or setting the {{Animation/startTime}} on a running animation, the animation continues to observe changes in 'animation-play-state'. * After successfully setting the {{Animation/effect}} of a {{CSSAnimation}} to null or some {{AnimationEffect}} other than the original {{KeyframeEffect}}, all subsequent changes to animation properties other than 'animation-name', 'animation-play-state', or 'animation-timeline' will not be reflected in that animation. Similarly, any change to matching ''@keyframes'' rules will not be reflected in that animation. However, if the last matching ''@keyframes'' rule is removed the animation must still be canceled. Note, the reference to a successful call in the above rules is necessary to ensure that when an exception is thrown by any of these methods, the override behavior is not applied. ## Owning element ## {#owning-element-section} The owning element of an animation refers to the element or pseudo-element to which the 'animation-name' property was applied that generated the animation. If the 'display' property of an element is set to ''display/none'' and its 'display' value would compute to ''display/none'' when ignoring the Transitions and Animations [=cascade origins=], then terminate running animations with this owning element. If an element has a 'display' of ''display/none'' and its 'display' value had computed to ''display/none'' when ignoring the Transitions and Animations [=cascade origins=], updating 'display' to a value other than ''display/none'' will start all animations applied to the element by the 'animation-name' property. Note: In practice, this means that an animation to a 'display' value of ''display/none'' will not terminate running animations unless the style also computes to ''display/none'' without the effect of the animations. If an animation generated using the markup defined in this specification is later disassociated from that markup by an update to the computed value of the 'animation-name' property on the owning element, the animation is disassociated from its owning element (that is, it has no owning element from that point forwards).
In the example below, animation's initial owning element is elem. animation is disassociated from element through an update to the computed value of elem's 'animation-name' property.
elem.style.animation = 'spin 1s';
let animation = elem.getAnimations()[0]; // animation's owning element is elem
elem.style.animation = ""; // animation no longer has an owning element
Note that although the owning element is often equal to the [=target element=] of an animation's [=associated effect=], this is not always the case. The following example demonstrates some of the situations where these two elements may differ.
elem.style.animation = 'move 1s';
let animation = elem.getAnimations()[0];
// animation.effect.target == elem == animation's owning element

animation.effect.target = elem2;
// animation.effect.target == elem2 != animation's owning element

animation.effect = null;
// animation.effect?.target is undefined != animation's owning element
## Animation composite order ## {#animation-composite-order} [=Animations=] generated from the markup defined in this specification have an animation class of ‘CSS Animation’. CSS Animations with an owning element have a later composite order than CSS Transitions but an earlier composite order than animations without a specific animation class. Within the set of CSS Animations with an owning element, two animations A and B are sorted in composite order (first to last) as follows: 1. If the owning element of A and B differs, sort A and B by tree order of their corresponding owning elements. With regard to pseudo-elements, the sort order is as follows: * element * ::marker * ::before * any other pseudo-elements not mentioned specifically in this list, sorted in ascending order by the Unicode codepoints that make up each selector * ::after * element children 1. Otherwise, sort A and B based on their position in the computed value of the 'animation-name' property of the (common) owning element. When determining the composite order in order to sort [[#events|animation events]] where either or both of the events is an {{animationcancel}} event, treat the CSS Animation(s) for which the {{animationcancel}} event was generated as having an [=owning element=] corresponding to the owning element in use at the moment when the CSS Animation was cancelled. Furthermore, use the position of the animation in the 'animation-name' property in effect at the time when the CSS Animation was cancelled sorting such that positions of cancelled animations sort before positions of animations that have not been cancelled. The composite order of CSS Animations without an owning element is based on their position in the global animation list. Issue: This differs from the behavior defined for transitions. We should probably sort transitions first, then animation, then use the global animation list. The reason being that when developer tools etc. hang on to orphaned animations and transitions in order to replay them, they should maintain roughly the same composite order. CSS Animations generated using the markup defined in this specification are not added to the global animation list when they are created. Instead, these animations are appended to the global animation list at the first moment when they transition out of the [=play state/idle=] play state after being disassociated from their owning element. CSS Animations that have been disassociated from their owning element but are still [=play state/idle=] do not have a defined composite order. Note, this behavior relies on the fact that disassociating an animation from its owning element always causes it to enter (or remain) in the [=play state/idle=] play state.

Assembling Keyframes

Declaring Keyframes: the ''@keyframes'' rule

See [[css-animations-1#keyframes]].

Processing Keyframes

For each animation effect defined by the Nth item in the [=coordinated value list=] of the 'animation-*' properties on target (pseudo-)element |element|, its associated [=keyframes=] are generated as follows: 1. Set Defaults: * Let |default timing function| be the corresponding [=computed value=] of 'animation-timing-function' on |element|. * Let |default composite| be the corresponding [=computed value=] of 'animation-composition' on |element|. * Let |keyframes| be an empty sequence of [=keyframe=] objects, each possessing a |keyframe offset|, |keyframe timing function|, |keyframe composite|, and |keyframe values|. * Let |animated properties| be an empty set of CSS [=property names=]. 1. Collect Declared Keyframes: 1. Find the last ''@keyframes'' at-rule in document order with <> matching the corresponding 'animation-name' value |name|. If there is no ''@keyframes'' at-rule with <> matching |name| (or if |name| is ''animation-name/none''), abort this procedure. In this case no animation is generated, and any existing animation matching |name| is canceled. 1. Group together all <> declarations that share the same [=specified value|specified=] <> (treating ''@keyframe/from'' as ''0%'' and ''@keyframe/to'' as ''100%''), last declared 'animation-timing-function' [=computed value=] (defaulting to |default timing function| if there is no such declaration), and last declared 'animation-composition' [=computed value=] (defaulting to |default composite| if there is no such declaration). 1. For each such group of matching <> declarations, ordered by their earliest <> in the sorted order: 1. [=Cascade=] together all of its [=declaration blocks=] such that for each CSS property (except those that are “not animatable”, which must be ignored) the last declaration among all its <> declarations takes precedence. [[CSS-CASCADE-4]] Note: The [=cascade=] will expand [=shorthand properties=] into their [=sub-properties=] and map together corresponding property pairs in each [=logical property group=] according to the |element|’s [=computed value|computed=] [=writing mode=]. 1. Append to |keyframes| a new empty [=keyframe=] with the group’s |keyframe offset|, |keyframe timing function|, and |keyframe composite|. Give its |keyframe values| the set of [=declared values=] resulting from this cascade. 1. Add each [=property name=] that was added to its {{CSSKeyframesRule/cssRules}} to |animated properties|. 1. Generate Initial and Final Frames: 1. Find or create the |initial keyframe|, a [=keyframe=] with a |keyframe offset| of ''0%'', |default timing function| as its |keyframe timing function|, and |default composite| as its |keyframe composite|. 1. For any property in |animated properties| that is not otherwise present in a keyframe with an offset of ''0%'' or one that would be positioned earlier in the [=used keyframe order=], add the [=computed value=] of that property on |element| to |initial keyframe|’s |keyframe values|. 1. If |initial keyframe|’s |keyframe values| is not empty, prepend |initial keyframe| to |keyframes|. 1. Repeat for |final keyframe|, using an offset of ''100%'', considering keyframes positioned later in the [=used keyframe order=], and appending to |keyframes|. 1. Sort Frames: * The specified order of |keyframes| is the order resulting from the steps above, i.e. document order with duplicate keyframes collapsed to the earliest position. * The computed order of |keyframes|-- which is the order returned by {{KeyframeEffect/getKeyframes()}}-- is found by shifting any keyframes whose offset was specified as a <>, ''@keyframes/from'' keyword, or ''@keyframes/to'' keyword to the front of the list (after the generated |initial keyframe|, if any), and performing a stable sort on these keyframes by their |keyframe offset|s. * The used order of |keyframes|-- which is the order used to interpolate and compute the actual animation frames-- is found by attaching the |keyframes| onto the animation effect’s timeline assuming an [=iteration count=] of 1 and ordering them from earliest to latest, breaking ties by using the [=computed keyframe order=]. Issue: Any specific requirements on sorting computed keyframes introduced by this spec should be integrated into [[web-animations-1#calculating-computed-keyframes]]. Any specific requirements on used keyframes introduced by this spec should be integrated into [[web-animations-1#the-effect-value-of-a-keyframe-animation-effect]]. The above description of the distinction between these sets of keyframes should be moved to an informative note. Note: Although the [=computed keyframe order=] sorts keyframes with <> offsets, it maintains keyframes specified with a <> in their [=specified keyframe order=]-- after any <> keyframes (other than a generated |final keyframe|), even if these come later in the [=used keyframe order=].

Declaring Animations

CSS Animations are defined by binding keyframes to an element using the 'animation-*' properties. These list-valued properties, which are all [=longhands=] of the 'animation' [=shorthand=], form a [=coordinating list property group=] with 'animation-name' as the [=coordinating list base property=] and each item in the [=coordinated value list=] defining the properties of a single animation effect. See [[css-values-4#linked-properties]] for how the individual 'animation-*' property values coordinate. ## The 'animation-duration' property ## {#animation-duration}
  Name: animation-duration
  Value: [ auto | <
The 'animation-duration' property specifies the [=iteration duration=] of the animation's associated [=animation effect=].
auto
For time-driven animations, equivalent to ''0s''. For [=scroll-driven animations=], equivalent to the duration necessary to fill the timeline in consideration of 'animation-range', 'animation-delay', and 'animation-iteration-count'. See [[scroll-animations-1#finite-attachment]].
<
For time-driven animations, specifies the length of time that an animation takes to complete one cycle. A negative <
If the [=used value|used=] 'animation-duration' is ''0s'', the animation itself still occurs (instantaneously). The animation’s start and end events are still fired. If 'animation-fill-mode' is set to ''single-animation-fill-mode/backwards'' or ''single-animation-fill-mode/both'', the first frame of the animation (as defined by 'animation-direction') will be displayed during the 'animation-delay'; and if 'animation-fill-mode' is set to ''single-animation-fill-mode/forwards'' or ''single-animation-fill-mode/both'', the last frame of the animation (as defined by 'animation-direction') will be displayed after the 'animation-delay'. However, if 'animation-fill-mode' is set to ''animation-fill-mode/none'' the keyframes of the animation animation will have no noticeable effect. For backwards-compatibility with Level 1, when the [=computed value=] of 'animation-timeline' is ''animation-timeline/auto'' (i.e. only one list value, and that value being ''animation-timeline/auto''), the [=resolved value=] of ''animation-duration/auto'' for 'animation-duration' is ''0s'' whenever its [=used value=] would also be ''0s''. ## The 'animation-timing-function' property ## {#animation-timing-function} The 'animation-timing-function' is used to determine the [=timing function=] applied to each [=keyframe=] as defined in [[#keyframes]]. ## The 'animation-iteration-count' property ## {#animation-iteration-count} The 'animation-iteration-count' property specifies the [=iteration count=] of the animation's associated [=animation effect=]. ## The 'animation-direction' property ## {#animation-direction} The 'animation-direction' property specifies the [=playback direction=] of the animation's associated [=animation effect=]. ## The 'animation-play-state' property ## {#animation-play-state} The 'animation-play-state' is used to pause or play the animation. If at any time, including when the animation is first generated, the resolved value of 'animation-play-state' corresponding to an animation is newly ''running'', the implementation must run the procedure to [=play an animation=] for the given animation with the auto-rewind flag set to false. If at any time, including when the animation is first generated, the resolved value of 'animation-play-state' corresponding to an animation is newly ''paused'', the implementation must run the procedure to [=pause an animation=] for the given animation. The above requirements do not apply if the animation's play state is being overridden by the Web Animations API as described in [[#animations]]. ## The 'animation-delay' property ## {#animation-delay} The 'animation-delay' property specifies the [=start delay=] of the animation's associated [=animation effect=]. ## The 'animation-fill-mode' property ## {#animation-fill-mode} The 'animation-fill-mode' property specifies the [=fill mode=] of the animation's associated [=animation effect=]. ## The 'animation-composition' property ## {#animation-composition} The 'animation-composition' property defines the composite operation used when multiple animations affect the same property simultaneously.
Name: animation-composition
Value: <>#
Initial: replace
Applies to: all elements
Inherited: no
Percentages: N/A
Computed value: list, each item a keyword as specified
Animation type: not animatable
Canonical order: per grammar
<single-animation-composition> = replace | add | accumulate The values of 'animation-composition' have the meaning defined for the corresponding values of the composite operation defined in Web Animations [[!WEB-ANIMATIONS]]. When specified in a keyframe, 'animation-composition' defines the composite operation to use for each property specified in that keyframe until the next keyframe specifying each property.
For example, the following stylesheet defines two different animations targeting the 'scale' property.
    @keyframes heartbeat {
      from {
        scale: 1;
        animation-timing-function: ease-out;
      }
      30% {
        scale: 1.3;
      }
    }
    .heartbeat {
      animation: heartbeat 0.3s 2s infinite;
    }

    @keyframes throb {
      50% {
        scale: 1.8;
      }
    }
    .icon:mouseover {
      animation: throb 0.4s add;
    }
  
If these two animations are applied to the same element, normally only one animation would apply, but by specifying ''add'' as the 'animation-composition' on the second animation, the result of the two animations will be combined. Since CSS Transitions [[CSS3-TRANSITIONS]] have a lower composite order, it is possible to use 'animation-composition' to combine CSS Animations with underlying transitions as in the following example.
    .icon {
      filter: blur(20px);
      transition: filter 0.5s;
    }
    .icon:hover {
      filter: blur(0px);
      animation: brightness-pulse 3s infinite add;
    }

    @keyframes brightness-pulse {
      0% {
        scale: 1.1;
        filter: brightness(130%);
      }
      10% {
        scale: 1;
        filter: brightness(100%);
      }
    }
  
Issue: Create pictures of these examples and verify they make sense.
## The 'animation-timeline' property ## {#animation-timeline} The 'animation-timeline' property defines the timeline used with the animation. Note: This specification does not introduce any syntax to specify animation timelines but instead it is up to others specifications such as Scroll-linked Animations [[SCROLL-ANIMATIONS]] to do so.
Name: animation-timeline
Value: <>#
Initial: auto
Applies to: all elements
Inherited: no
Percentages: N/A
Computed value: list, each item either
    the keyword ''single-animation-timeline/none'',
    the keyword ''single-animation-timeline/auto'',
    a case-sensitive [=css identifier=],
    a computed ''scroll()'' function,
    or
    a computed ''view()'' function
Canonical order: per grammar
Animation Type: not animatable
<single-animation-timeline> = auto | none | <> | <> | <>
The 'animation-timeline' property is similar to properties like 'animation-name' and 'animation-duration' in that it can have one or more values, each one imparting additional behavior to a corresponding [=animation=] on the element, with the timelines matched up with animations as described [[css-animations-1#animation-name|here]]. Each value has type <>, whose possible values have the following effects:
: auto :: The animation's [=timeline=] is a {{DocumentTimeline}}, more specifically the default document timeline. : none :: The animation is not associated with a [=timeline=]. : <> :: If a named [=scroll progress timeline=] or [=view progress timeline=] is in scope on this element, use the referenced timeline as defined in [[scroll-animations-1#timeline-scope]]. Otherwise the animation is not associated with a [=timeline=]. : <> :: Use the [=scroll progress timeline=] indicated by the given ''scroll()'' function. See [[scroll-animations-1#scroll-notation]]. : <> :: Use the [=view progress timeline=] indicated by the given ''view()'' function. See [[scroll-animations-1#view-notation]].
Issue: Make it easier to use 'animation-name' to select the timeline when 'animation-timeline' is not specified. Allowing 'animation-name' to be used for selecting timeline enables most common animations to have to use a single name for both their keyframes and timeline which is simple and ergonomics. The 'animation-timeline' property gives authors additional control to independently select keyframes and timeline if necessary. When multiple 'animation-*' properties are set simultaneously, 'animation-timeline' is updated first, so e.g. a change to 'animation-play-state' applies to the simultaneously-applied timeline specified in 'animation-timeline'. ## The 'animation' shorthand property ## {#animation-shorthand} The 'animation' shorthand property syntax is as follows: <single-animation> = <<'animation-duration'>> || <> || <<'animation-delay'>> || <> || <> || <> || <> || [ none | <> ] || <> # Animation Events # {#events} ## Event dispatch ## {#event-dispatch} Note, this is a more general description of event dispatch than that of CSS Animations Level 1 [[CSS3-ANIMATIONS]] since it must account for the possibility of animations being seeked or reversed using the Web Animations API [[WEB-ANIMATIONS]]. The [=event target|target=] for a CSS animation event is the animation's [=owning element=]. If there is no [=owning element=], no CSS animation events are dispatched (although the [=animation playback events=] defined in Web Animations are still dispatched at the corresponding {{CSSAnimation}} object). For the purpose of determining which events to dispatch, the [[web-animations-1#animation-effect-phases-and-states|phases]] defined in the Web Animations model are used. These definitions apply to an animation effect, however, for the purpose of dispatching events, we consider a CSS Animation to have the same phase as its [=associated effect=]. For example, a CSS Animation is in the [=animation effect/before phase=] if its [=associated effect=] is in the [=animation effect/before phase=]. A CSS Animation that does not have an [=associated effect=] is considered to be in the idle phase if its [=animation/current time=] is unresolved, in the [=animation effect/before phase=] if its current time is less than zero, and in the [=animation effect/after phase=] otherwise. Similarly, subsequent references to the start delay, active duration, current iteration, iteration start, and iteration duration of a CSS animation should be understood to refer to the corresponding properties of the animation's [=associated effect=]. For calculating the {{AnimationEvent/elapsedTime}} of each event, the following definitions are used: * interval start = max(min(-start delay, active duration), 0) * interval end = max(min([=associated effect end=] - start delay, active duration), 0) Each time a new [=animation frame=] is established and the animation does not have a [=pending play task=] or [=pending pause task=], the events to dispatch are determined by comparing the animation's phase before and after establishing the new [=animation frame=] as follows:
Change Events dispatched Elapsed time (ms)
[=animation effect/idle phase|idle=] or [=animation effect/before phase|before=] → [=animation effect/active phase|active=] {{animationstart}} interval start
[=animation effect/idle phase|idle=] or [=animation effect/before phase|before=] → [=animation effect/after phase|after=] ٭ {{animationstart}} interval start
{{animationend}} interval end
[=animation effect/active phase|active=] → [=animation effect/before phase|before=] {{animationend}} interval start
[=animation effect/active phase|active=] → [=animation effect/active phase|active=] and the current iteration of the animation's [=associated effect=] has changed since the previous animation frame {{animationiteration}} (See below)
[=animation effect/active phase|active=] → [=animation effect/after phase|after=] {{animationend}} interval end
[=animation effect/after phase|after=] → [=animation effect/active phase|active=] {{animationstart}} interval end
[=animation effect/after phase|after=] → [=animation effect/before phase|before=] ٭ {{animationstart}} interval end
{{animationend}} interval start
not [=animation effect/idle phase|idle=] and not [=animation effect/after phase|after=] → [=animation effect/idle phase|idle=] {{animationcancel}} The active time of the animation at the moment it was cancelled calculated using a fill mode of both.

٭ Where multiple events are listed for a state change, all events are dispatched in the order listed and in immediate succession.

† The elapsed time for an {{animationiteration}} event is defined as follows:

1. Let previous current iteration be the current iteration from the previous animation frame. 1. If previous current iteration is greater than current iteration, let iteration boundary be current iteration + 1, otherwise let it be current iteration. 1. The elapsed time is the result of evaluating (iteration boundary - iteration start) × iteration duration). Since the elapsed time defined in the table and procedure above is expressed in milliseconds, it must be divided by 1,000 to produce a value in seconds before being assigned to the {{AnimationEvent/elapsedTime}} member of the {{AnimationEvent}}. ## The AnimationEvent Interface ## {#interface-animationevent} ### IDL Definition ### {#interface-animationevent-idl} Add {{AnimationEvent/animation}} to the {{AnimationEvent}} interface and {{AnimationEventInit}} dictionary as follows:
[Exposed=Window]
partial interface AnimationEvent {
  readonly attribute CSSAnimation? animation;
};

partial dictionary AnimationEventInit {
  CSSAnimation? animation = null;
};
### Attributes ### {#interface-animationevent-attributes} Add attribute descriptions as follows:
animation
The CSS Animation that fired the event.
# DOM Interfaces # {#interface-dom} ## The CSSAnimation interface ## {#the-CSSAnimation-interface}
[Exposed=Window]
interface CSSAnimation : Animation {
  readonly attribute CSSOMString animationName;
};
: animationName :: The key used to find matching keyframes rules that define the [=associated effect=] at the point when the animation was created. This is the value of the 'animation-name' property that caused this object to be generated. ## Requirements on pending style changes ## {#requirements-on-pending-style-changes} Various operations may affect the computed values of properties on elements. User agents may, as an optimization, defer recomputing these values until it becomes necessary. However, all operations included in programming interface defined in this specification, as well as those operations defined in Web Animations [[!WEB-ANIMATIONS]] that may return objects or animation state defined by this specification, must produce a result consistent with having fully processed any such pending changes to computed values.
As an example, in the following code fragment, when the specified style of elem is initially updated, a user agent may defer recalculating the computed value of the 'animation' property. However, the {{Animatable/getAnimations()}} method called on elem is specified by Web Animations and can return {{CSSAnimation}} objects as defined in this specification. Hence, as result of the requirements in this section, the user agent must calculate the updated value of elem's 'animation' property and create the requested {{CSSAnimation}} object before returning its result.
elem.style.animation = 'fadeOut 1s';
elem.getAnimations()[0].pause();
Similarly, reading {{Animation/playState}} may depend on pending style changes.
elem.style.animation = 'fadeOut 1s paused';
const anim = elem.getAnimations()[0];
elem.style.animationPlayState = 'running';
console.log(anim.playState); // Should be 'running'.

Privacy Considerations

No privacy concerns have been reported on this specification.

Security Considerations

No security concerns have been reported on this specification.

Changes

Recent Changes

Changes since the 2 June 2023 Working Draft:

  • Moved the animation-trigger property to a new spec, animation-triggers-1 (PR 13571)
  • Define trigger scope. Flattened tree; removed anchor-scope reference (PR 13241)
  • Added play-once animation-action (Issue 12611)
  • Defined that event triggers can be defined to have enter/exit pairs, like timelines.
  • Separated trigger concept from trigger instance
  • Changed initial value of the exit ranges to 'auto', to match the start ranges
  • Changed "animation-trigger-behavior" to "animation-trigger" and largely rewrote the definition (PR 13009)
  • Changed animation-trigger-type to animation-trigger-behavior (PR 12223)
  • Clarified that setting "effect" should not prevent the timeline to set "set" via animation-timeline (PR 11812)
  • Defined animation-trigger-* as reset-only sub-properties of animation (PR 11653)
  • Added note to Animation Frames about running the updating animation trigger state procedure
  • Added algorithm for Setting a Trigger of an Animation
  • Added the AnimationTrigger interface
  • Moved all new definitions from web-animations-1 to web-animations-2
  • Specified the animation-trigger property (Issue 8942)
  • Defined order for sorting animationcancel events (Issue 11064)
  • Made animation-duration:auto resolve to 0s, for legacy compat (Issue 6530)
  • Switched timeline names from <> to <> (Issue 8746)

Changes since the 2 March 2023 Working Draft:

  • Added ''animation-duration/auto'' as the [=initial value=] of 'animation-duration'. (Issue 6530)
  • Rewrote [[#keyframe-processing]] to re-use the [=cascade=], to handle non-percentage keyframe offsets, to handle keyframes with offsets outside the [0,1] range, and to use the value of 'animation-composition' as the default composite.
  • Reduced the cases where ''display: none'' cancel an animation. (Issue 6429)
  • Cross-linked to [[css-values-4#linked-properties]] to define how the various 'animation-*' properties interact.
  • Clarified that among the animation properties, 'animation-timeline' is applied first.

Changes since CSS Animations, Level 1

  • The interaction between CSS Animations and Web Animations is defined, and the concepts of the owning element and animation composite order are introduced.
  • Generation of keyframe objects is described in detail.
  • The 'animation-composition' property is introduced, which defines the composite operation used when multiple animations affect the same property simultaneously.
  • The 'animation-timeline' property is introduced, which defines the timeline used with the animation.
  • The 'animation' shorthand property is updated to account for these new properties.
  • Dispatch of animation events is described.
  • The {{CSSAnimation}} interface is added.
  • Requirements on pending style changes are described.