CSS Animations Level 2

Editor’s Draft,

This version:
http://dev.w3.org/csswg/css-animations-2/
Feedback:
www-style@w3.org with subject line “[css-animations-2] … message topic …” (archives)
Issue Tracking:
GitHub
Inline In Spec
Editor:
(Mozilla)
Issues List:
In Bugzilla

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.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.

Status of this document

This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.

The (archived) public mailing list www-style@w3.org (see instructions) is preferred for discussion of this specification. When sending e-mail, please put the text “css-animations-2” in the subject, preferably like this: “[css-animations-2] …summary of comment…

This document was produced by the CSS Working Group (part of the Style Activity).

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 September 2015 W3C Process Document.

Table of Contents

1. 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.

2. Animations

2.1. Owning element

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 an animation was generated directly by script (e.g. using the CSSAnimation constructor) then it has no owning element.

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 target 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

let mutableEffect = animation.effect.clone();
animation.effect = mutableEffect;
animation.effect.target = elem2;
// animation.effect.target == elem2 != animation’s owning element

animation.effect = null;
// animation.effect.target is undefined != animation’s owning element

2.2. Animation composite order

Animations generated from the markup or interfaces (e.g. the CSSAnimation constructor) defined in this specification have an animation type 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 type.

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

    • ::before

    • ::after

    • element children

  2. Otherwise, sort A and B based on their position in the computed value of the animation-name property of the (common) owning element.

The composite order of CSS Animations without an owning element is based on their position in the global animation list.

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 idle play state after being disassociated from their owning element. CSS Animations that have been disassociated from their owning element but are still 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 idle play state.

CSS Animations created using the CSSAnimation constructor are appended to the global animation list at the moment they are constructed.

3. Keyframes

3.1. The animation-play-state property

3.1.1. Interaction between animation-play-state and the Web Animations API

Both this specification and the Web Animations specification [WEB-ANIMATIONS] define mechanisms for pause control, specifically the animation-play-state property, and the play() and pause() methods respectively.

The interaction of these methods can be summarized as follows:

With regards to the pausing, an animation can be considered to be in one of five mutually-exclusive states:

A state transition chart follows:

Initial state
Event A B C D E
Resulting state play() A B A B B
pause() C D C D D
animation-play-staterunning A A C C A
animation-play-statepaused E B D D E

If any change causes an animation to change from one of the running states (A, B) to one of the paused states (C, D, E), the user agent must run the pause an animation procedure on the animation.

Likewise, for any change from one of the the paused states to one of the running states, the user agent must run the play an animation procedure on the animation. If the change is due to a change in the computed value of animation-play-state (i.e. the transition E → A) the auto-rewind flag for that procedure must be set to false; otherwise it must be set to true.

3.2. The animation-composition property

The animation-composition property defines the composite operation used when multiple animations affect the same property simultaneously.

Name: animation-composition
Value: <single-animation-composition>#
Initial: replace
Applies to: all elements, ::before and ::after pseudo-elements
Inherited: none
Percentages: N/A
Media: interactive
Computed value: As specified
Animatable: no
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 targetting 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 pulse {
  0% {
    scale: 1.1;
    filter: brightness(130%);
  }
  10% {
    scale: 1;
    filter: brightness(100%);
  }
}

Create pictures of these examples and verify they make sense.

4. Animation Events

4.1. Types of AnimationEvent

The additional types of animation events that can occur are:

animationcancel
The animationcancel event occurs when the animation stops running in a way that does not fire an animationend event, such as a change in the animation-name that removes the animation, or the animating element or one of its ancestors becoming display:none.
  • Bubbles: Yes
  • Cancelable: No
  • Context Info: animationName, elapsedTime, pseudoElement

4.2. 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 using the Web Animations API [WEB-ANIMATIONS].

For the purpose of determining which events to dispatch, an animation can be considered to be in one of four mutually-exclusive event states determined using the following procedure:

  1. If the animation is idle or has no target effect it is idle.

  2. Otherwise, if the animation has a current time less than the start delay of its target effect, or, if the animation’s playback rate is less than zero and it has a current time less than or equal to the start delay of its target effect, it is left-active.

  3. Otherwise, if the animation has a current time greater than its target effect end, or, if the animation’s playback rate is greater than or equal to zero and it has a current time greater than or equal to its target effect end, it is right-active.

  4. Otherwise, it is active.

Each time the animation is sampled, the events to dispatch are determined by comparing the event state before and after the sample as follows:

not activeactive

animationstart

left-activeright-active

right-activeleft-active

animationstart, animationend

activeleft-active

activeright-active

animationend

activeactive

animationiteration if there has been a change to the current iteration of the animation’s target effect.

not idleidle

animationcancel

Define the value of elapsedTime for each case.

5. DOM Interfaces

5.1. The CSSAnimation interface

interface CSSAnimation : Animation {
  readonly attribute DOMString animationName;
};

animationName, of type DOMString, readonly

The key used to find matching keyframes rules that define target 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 or, if this object was generated using the programming interface, the animationName argument that was passed to the CSSAnimation constructor.

We need to define a constructor for CSSAnimation. Perhaps something like the following:

[Constructor (Animatable? target,
              DOMString animationName,
              optional (unrestricted double or KeyframeEffectOptions) options,
              optional DOMString defaultEasing = "ease"),
 Constructor (Animatable? target,
              DOMString animationName,
              (unrestricted double or KeyframeEffectOptions) options,
              DOMString defaultEasing,
              AnimationTimeline? timeline)]
partial interface CSSAnimation { };

The difficulty is with liveness. The most useful and least magical (but most complicated) approach is to define a subclass of KeyframeEffectReadOnly that has the special behavior of tracking changes to all @keyframes rules that match the supplied name and automatically updating the set of keyframes returned by getFrames() after filling-in the default easing.

Something like,

[Constructor (DOMString keyframesName, DOMString defaultEasing)]
interface CSSKeyframeEffectReadOnly : KeyframeEffectReadOnly {
  readonly attribute DOMString keyframesName;
  readonly attribute DOMString defaultEasing;
};

5.2. 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 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 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();

Conformance

Document conventions

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words "for example" or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word "Note" and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

Advisements are normative sections styled to evoke special attention and are set apart from other normative text with <strong class="advisement">, like this: UAs MUST provide an accessible alternative.

Conformance classes

Conformance to this specification is defined for three conformance classes:

style sheet
A CSS style sheet.
renderer
A UA that interprets the semantics of a style sheet and renders documents that use them.
authoring tool
A UA that writes a style sheet.

A style sheet is conformant to this specification if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.

A renderer is conformant to this specification if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by this specification by parsing them correctly and rendering the document accordingly. However, the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)

An authoring tool is conformant to this specification if it writes style sheets that are syntactically correct according to the generic CSS grammar and the individual grammars of each feature in this module, and meet all other conformance requirements of style sheets as described in this module.

Partial implementations

So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported component values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored.

Experimental implementations

To avoid clashes with future CSS features, the CSS2.1 specification reserves a prefixed syntax for proprietary and experimental extensions to CSS.

Prior to a specification reaching the Candidate Recommendation stage in the W3C process, all implementations of a CSS feature are considered experimental. The CSS Working Group recommends that implementations use a vendor-prefixed syntax for such features, including those in W3C Working Drafts. This avoids incompatibilities with future changes in the draft.

Non-experimental implementations

Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.

To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before releasing an unprefixed implementation of any CSS features. Testcases submitted to W3C are subject to review and correction by the CSS Working Group.

Further information on submitting testcases and implementation reports can be found from on the CSS Working Group’s website at http://www.w3.org/Style/CSS/Test/. Questions should be directed to the public-css-testsuite@w3.org mailing list.

Index

Terms defined by this specification

Terms defined by reference

References

Normative References

[WebIDL]
Cameron McCormack; Boris Zbarsky. WebIDL Level 1. 4 August 2015. WD. URL: http://www.w3.org/TR/WebIDL-1/
[CSS-ANIMATIONS-1]
CSS Animations Module Level 1 URL: http://www.w3.org/TR/css3-animations/
[CSS-CASCADE-4]
Elika Etemad; Tab Atkins Jr.. CSS Cascading and Inheritance Level 4. 8 September 2015. WD. URL: http://www.w3.org/TR/css-cascade-4/
[CSS-MASKING-1]
Dirk Schulze; Brian Birtles; Tab Atkins Jr.. CSS Masking Module Level 1. 26 August 2014. CR. URL: http://www.w3.org/TR/css-masking-1/
[CSS-TRANSFORMS-2]
CSS Transforms Module Level 2 URL: https://drafts.csswg.org/css-transforms-2/
[CSS-VALUES]
Tab Atkins Jr.; Elika Etemad. CSS Values and Units Module Level 3. 11 June 2015. CR. URL: http://www.w3.org/TR/css-values/
[CSS3-ANIMATIONS]
Dean Jackson; et al. CSS Animations. 19 February 2013. WD. URL: http://www.w3.org/TR/css3-animations/
[DOM-LS]
Document Object Model URL: https://dom.spec.whatwg.org/
[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
[WEB-ANIMATIONS]
Brian Birtles; et al. Web Animations. 7 July 2015. WD. URL: http://www.w3.org/TR/web-animations-1/
[WEB-ANIMATIONS-1]
Brian Birtles; et al. Web Animations. 7 July 2015. WD. URL: http://www.w3.org/TR/web-animations-1/

Informative References

[CSS3-TRANSITIONS]
Dean Jackson; et al. CSS Transitions. 19 November 2013. WD. URL: http://www.w3.org/TR/css3-transitions/

Property Index

Name Value Initial Applies to Inh. %ages Media Animatable Canonical order Computed value
animation-composition <single-animation-composition># replace all elements, ::before and ::after pseudo-elements none N/A interactive no per grammar As specified

IDL Index

interface CSSAnimation : Animation {
  readonly attribute DOMString animationName;
};

[Constructor (Animatable? target,
              DOMString animationName,
              optional (unrestricted double or KeyframeEffectOptions) options,
              optional DOMString defaultEasing = "ease"),
 Constructor (Animatable? target,
              DOMString animationName,
              (unrestricted double or KeyframeEffectOptions) options,
              DOMString defaultEasing,
              AnimationTimeline? timeline)]
partial interface CSSAnimation { };

[Constructor (DOMString keyframesName, DOMString defaultEasing)]
interface CSSKeyframeEffectReadOnly : KeyframeEffectReadOnly {
  readonly attribute DOMString keyframesName;
  readonly attribute DOMString defaultEasing;
};

Issues Index

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.
Create pictures of these examples and verify they make sense.
Define the value of elapsedTime for each case.

We need to define a constructor for CSSAnimation. Perhaps something like the following:

[Constructor (Animatable? target,
              DOMString animationName,
              optional (unrestricted double or KeyframeEffectOptions) options,
              optional DOMString defaultEasing = "ease"),
 Constructor (Animatable? target,
              DOMString animationName,
              (unrestricted double or KeyframeEffectOptions) options,
              DOMString defaultEasing,
              AnimationTimeline? timeline)]
partial interface CSSAnimation { };

The difficulty is with liveness. The most useful and least magical (but most complicated) approach is to define a subclass of KeyframeEffectReadOnly that has the special behavior of tracking changes to all @keyframes rules that match the supplied name and automatically updating the set of keyframes returned by getFrames() after filling-in the default easing.

Something like,

[Constructor (DOMString keyframesName, DOMString defaultEasing)]
interface CSSKeyframeEffectReadOnly : KeyframeEffectReadOnly {
  readonly attribute DOMString keyframesName;
  readonly attribute DOMString defaultEasing;
};