Timing control for script-based animations

W3C Candidate Recommendation 31 October 2013

This Version:
Latest Published Version:
Latest Editor’s Draft:
Previous Version:
James Robinson, Google, Inc <jamesr@chromium.org>
Cameron McCormack, Mozilla Corporation <cam@mcc.id.au>


This document defines an API web page authors can use to write script-based animations where the user agent is in control of limiting the update rate of the animation. The user agent is in a better position to determine the ideal animation rate based on whether the page is currently in a foreground or background tab, what the current load on the CPU is, and so on. Using this API should therefore result in more appropriate utilization of the CPU by the browser.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

W3C publishes a Candidate Recommendation to indicate that the document is believed to be stable and to encourage implementation by the developer community.

The entrance criteria for this document to enter the Proposed Recommendation stage is to have a minimum of two independent and interoperable user agents that implement all the features of this specification, which will be determined by passing the user agent tests defined in the test suite developed by the Working Group. No feature in this document is marked at-risk.

The Working Group does not expect to advance to Proposed Recommendation prior to . A preliminary implementation report is available and will be updated during the Candidate Recommendation period. This is a work in progress and may change without any notices.

The Working Group intends to gain implementation experience before recommending that implementations remove their vendor prefixes.

Please send comments about this document to public-web-perf@w3.org (archived) with [RequestAnimationFrame] at the start of the subject line.

This document is produced by the Web Performance Working Group. Changes made to this document can be found in the W3C public Mercurial server.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

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.

Table of Contents

1. Introduction

This section is informative.

Animations in web browsers come in two forms: native, declarative ones, such as the <animate> element in SVG, and those that are implemented in script. These script-based animations are most often performed by scheduling a callback using setTimeout or setInterval and making changes to the DOM to effect the animation in that callback.

A disadvantage of this approach is that the author of the animation script has no idea what the ideal frequency for updating their animation is. Instead, the easiest way forward for the author is to simply call setTimeout with a very small value, which in practice will be clamped to some minimum time like 10ms anyway. It likely won’t be the case that 100 updates per second are required for the animation, especially if the page is in a background tab or the browser window is minimized.

The API described in this document allows script authors to request the user agent schedule an animation frame update. The user agent is in a better position to determine how many frames per second to allocate to all of the animations running in the entire browser. If there are many animations active, the user agent can select a frame rate such that all of the animations will run as smoothly as possible. If the page is not currently visible, animations on that page can be throttled heavily so that they do not update often and thus consume little CPU power.


Here is an example of using the API to write a script-based animation.

<!DOCTYPE html>
<title>Script-based animation using requestAnimationFrame</title>
div { position: absolute; left: 10px; padding: 50px;
  background: crimson; color: white }
var requestId = 0;

function animate(time) {
  document.getElementById("animated").style.left =
    (time - animationStartTime) % 2000 / 4 + "px";
  requestId = window.requestAnimationFrame(animate);
function start() {
  animationStartTime = window.performance.now();
  requestId = window.requestAnimationFrame(animate);
function stop() {
  if (requestId)
  requestId = 0;
<button onclick="start()">Click me to start!</button>
<button onclick="stop()">Click me to stop!</button>
<div id="animated">Hello there.</div>

2. Conformance

Everything in this specification is normative except for diagrams, examples, notes and sections marked as being informative.

The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY” and “OPTIONAL” in this document are to be interpreted as described in Key words for use in RFCs to Indicate Requirement Levels. [RFC2119]

The IDL fragment in section 4 of this specification MUST be interpreted as required for conforming IDL fragments, as described in the Web IDL specification. [WEBIDL]

This specification defines a single conformance class:

conforming user agent
A user agent is considered to be a conforming user agent if it satisfies all of the MUST-, REQUIRED- and SHALL-level criteria in this specification. A conforming user agent MUST also be a conforming implementation of the IDL fragment in section 4 of this specification, as described in the Web IDL specification. [WEBIDL]

This specification references interfaces and types from a number of other specifications:

3. Definitions

Associated with every Document is an animation frame request callback list, which is a list of <handle, callback> tuples. handle is an integer that uniquely identifies the entry in the list. callback is a FrameRequestCallback object. Initially, the animation frame request callback list for a Document is empty.

A Document is said to have active animations whenever it has a non-empty animation frame request callback list.

4. Window interface extensions

The partial interface in the IDL fragment below is used to expose the requestAnimationFrame operation on the Window object. In the definition of requestAnimationFrame below, references to the Document object are to be taken to be references to the Window object’s active document. [HTML5]

partial interface Window {
  long requestAnimationFrame(FrameRequestCallback callback);
  void cancelAnimationFrame(long handle);

callback FrameRequestCallback = void (DOMHighResTimeStamp time);

The requestAnimationFrame method is used to signal to the user agent that a script-based animation needs to be resampled. When requestAnimationFrame(callback) is called, the user agent MUST schedule a script-based animation resampling by appending to the end of the animation frame request callback list an entry whose handle is a user-agent-defined integer greater than zero that uniquely identifies the entry in the list and whose callback is callback.

Each FrameRequestCallback object has a cancelled boolean flag. This flag is initially false and is not exposed by any interface.


requestAnimationFrame only schedules a single update to the script-based animation. If subsequent animation frames are needed, then requestAnimationFrame will need to be called again from within the callback.

Also note that multiple calls to requestAnimationFrame with the same callback (before callbacks are invoked and the list is cleared) will result in multiple entries being in the list with that same callback, and thus will result in that callback being invoked more than once for the animation frame.

The cancelAnimationFrame method is used to cancel a previously made request to schedule an animation frame update. When cancelAnimationFrame(handle) is called, the user agent MUST set the cancelled flag to true for the callback registered on this Document whose handle is handle. The cancelled flag is set whether the callback is in a animation frame request callback list or not. If there is no callback with the given handle, then this function does nothing.


cancelAnimationFrame might be called for an entry in the Document’s animation frame request callback list or in the sample all animations operation’s temporary list. In either case the entry’s cancelled flag is set to true so that the callback does not run.

5. Processing Model

Whenever a Document's hidden attribute ([Page Visibility]) is false and the animation frame request callback list is not empty, the user agent MUST regularly queue a task that samples all animations for that Document's top-level browsing context. The task source for these tasks is the animation task source. Only one task should be generated per top-level browsing context, even if multiple Documents within the same top-level browsing context are not hidden and contain callbacks. To samples all animations , the following steps are performed:
  1. Let list be an empty animation frame request callback list.
  2. Let contexts be the results of list of the descendant browsing contexts algorithm for this task's top-level browsing context.
  3. For every context in contexts, in any order, perform the following steps:
    1. Let time be the result of invoking the now method of the Performance interface within this context.
    2. Let d be context's active document.
    3. If d's hidden attribute is true, continue to the next entry in the contexts list. Otherwise proceed with these steps.
    4. Let doclist be d's animation frame request callback list.
    5. Append all entries from doclist into list preserving order.
    6. Clear doclist.
  4. Perform the steps defined in the invoke callbacks algorithm with parameter list.

The invoke callbacks algorithm:

  1. For each entry callback in list, in order:
    1. If the cancelled flag on callback is not true:
      1. Call callback with the callback's context's time as the argument.
      2. If calling the operation resulted in an exception being thrown, then catch that exception and ignore it.

The expectation is that the user agent will run tasks from the animation task source at at a regular interval matching the display's refresh rate. Running tasks at a lower rate can result in animations not appearing smooth. Running tasks at a higher rate can cause extra computation to occur without a user-visible benefit.

6. Acknowledgements

This section is informative.

The editors would like to thank the following people for contributing to this specification: Boris Zbarsky, Jonas Sicking, Robert O’Callahan.

This specification was written based on the mozRequestAnimationFrame feature implemented in Firefox.

A. References

A.1. Normative references

Document Object Model Level 3 Core Specification, A. Le Hors, et al., Editors. World Wide Web Consortium, 7 April 2004. This version of the Document Object Model Level 3 Core Recommendation is http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407. The latest version of DOM Core is available at http://www.w3.org/TR/domcore/.
HTML5, Robin Berjon et al., Editors. World Wide Web Consortium, August 2013. The latest version of HTML is available from http://www.w3.org/TR/html/. The latest editor's draft of HTML5 is available at http://www.w3.org/html/wg/drafts/html/CR/.
Page Visibility (Second Edition). Jatinder Mann, Editor. W3C Recommendation, World Wide Web Consortium, October 2013. Available at http://www.w3.org/TR/2013/REC-page-visibility-20131029/. Latest version is available at http://www.w3.org/TR/hr-time/
Key words for use in RFCs to Indicate Requirement Levels, S. Bradner. IETF, March 1997. Available at http://www.ietf.org/rfc/rfc2119.
[Web IDL]
Web IDL, Cameron McCormack, Editor. World Wide Web Consortium, April 2012. This version of the Web IDL specification is available from http://www.w3.org/TR/2012/CR-WebIDL-20120419/. The latest version of Web IDL is available at http://www.w3.org/TR/WebIDL/.
High Resolution Time. Jatinder Mann, Editor. W3C Recommendation, World Wide Web Consortium, December 2012. Available at http://www.w3.org/TR/2012/REC-hr-time-20121217/. Latest version is available at http://www.w3.org/TR/hr-time/