Retrieving requestAnimationFrame with JavaScript

By  on  

The requestAnimationFrame function has been a major boost to developers creating and managing animations with JavaScript.  Paul Irish has an excellent introduction on requestAnimationFrame -- I highly recommend you read it.  This HTML5Hub post is also very good.  Most browsers now support the animation function but in the case a browser doesn't, you can shim a rough equivalent with setInterval:

var requestAnimationFrame = window.requestAnimationFrame
    || window.webkitRequestAnimationFrame
    || window.mozRequestAnimationFrame
    || window.msRequestAnimationFrame
    || function(callback) { return setTimeout(callback, 1000 / 60); };

requestAnimationFrame was implemented with browser prefixes so we'll check for those if the unprefixed window method isn't there.  If no native implementation exists, a setInterval shim will have to do!

Recent Features

  • By
    CSS Animations Between Media Queries

    CSS animations are right up there with sliced bread. CSS animations are efficient because they can be hardware accelerated, they require no JavaScript overhead, and they are composed of very little CSS code. Quite often we add CSS transforms to elements via CSS during...

  • By
    An Interview with Eric Meyer

    Your early CSS books were instrumental in pushing my love for front end technologies. What was it about CSS that you fell in love with and drove you to write about it? At first blush, it was the simplicity of it as compared to the table-and-spacer...

Incredible Demos

  • By
    Morphing Elements Using MooTools and CSS

    Morphing an element between CSS classes is another great trick the MooTools JavaScript library enables you to do. Morphing isn't the most practical use of MooTools, but it's still a trick at your disposal. Step 1: The XHTML The block of content that will change is...

  • By
    MooTools TextOverlap Plugin

    Developers everywhere seem to be looking for different ways to make use of JavaScript libraries. Some creations are extremely practical, others aren't. This one may be more on the "aren't" side but used correctly, my TextOverlap plugin could add another interesting design element...

Discussion

  1. MaxArt

    According to caniuse, Microsoft’s browsers never had a vendor prefixed version of requestAnimationFrame, so we can just keep moz and webkit.

    That’s a very common way to normalize the function, but in most recent implementations requestAnimationFrame passes an argument to the callback function, which is the amount of milliseconds since performance.timing.navigationStart, with micro precision too. This can be very handy for the callback.

    It’s not really possible to perfectly emulate this, but you can get something close if you take note of the epoch time as soon as the script is executed. So this is how I used to polyfill requestAnimationFrame:

    (function(start) {
        window.requestAnimationFrame = function(callback) {
            return setInterval(function() {
                callback(new Date().getTime() - start);
            }, 1000 / 60);
        };
    })(new Date().getTime());
    

    (Well, not exactly… since most of the times requestAnimationFrame is called again in the callback function, but the function itself takes some milliseconds at least to be executed – because it probably involves some kind of repaint – and you should adjust the time interval accordingly, or you may never hope to even get close to 60 fps.)

    Also, don’t forget to normalize cancelAnimationFrame, which has a nasty variant in some (and maybe forgotten?) WebKit browsers: webkitCancelRequestAnimationFrame.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!