Provides requestAnimationFrame in a cross browser way.

RequestAnimationFrame.js

/**
 * Provides requestAnimationFrame in a cross browser way.
 * @author paulirish / http://paulirish.com/
 */

if ( !window.requestAnimationFrame ) {

	window.requestAnimationFrame = ( function() {

		return window.webkitRequestAnimationFrame ||
		window.mozRequestAnimationFrame ||
		window.oRequestAnimationFrame ||
		window.msRequestAnimationFrame ||
		function( /* function FrameRequestCallback */ callback, /* DOMElement Element */ element ) {

			window.setTimeout( callback, 1000 / 60 );

		};

	} )();

}

I cant understand one thing, why do we need to use the delay as 1000/60 why not just the resulting figure that evaluates by dividing 1000 by 60 what if I just put any round figure, and does animationFrameRate help us slowing down the animation without the setTimeout function, and under what conditions should we use it this way setTimeout(callback, 1000 / 60); and not setTimeout(callback, 1000);

Hi @mrdoob, why do we need the /* DOMElement Element */ element in the function?

@buttflattery I know this is an old post, but I'm replying for any future people who see this. You use 1000 / 60 because it results to around 16.667 milliseconds. If you were to use this number, it would call the render function almost exactly 60 times per second, meaning 60 FPS. You could easily do 1000 / 80 to get 80 FPS if you really wanted, but 60 FPS is a common number for monitor refresh rates. If you were to use 1000 as the delay, then you would only get 1 frame per second.