Bug Tracker

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#8101 closed enhancement (fixed)

use requestAnimationFrame instead of setInterval for animations, when available

Reported by: lrbabe Owned by: timmywil
Priority: blocker Milestone: 1.6
Component: effects Version: 1.5
Keywords: Cc: jaubourg
Blocked by: Blocking:


requestAnimationFrame is a mechanism meant to tell the browser that you wish to perform an animation; this requests that the browser schedule a repaint of the window for the next animation frame.

Full description here: https://developer.mozilla.org/en/DOM/window.mozRequestAnimationFrame


  • let the browser choose the best 'animation tick' rate (instead of our arbitrary 13ms)
  • greatly reduce animation CPU usage when switching tab
  • helps keep animation synchronized

Full list of claimed benefits here: http://hacks.mozilla.org/2010/08/more-efficient-javascript-animations-with-mozrequestanimationframe/

Currently supported in Firefox, chromium and Chrome dev channel.

Adding it to jQuery is a minor change (7 lines of Javascript).

Change History (11)

comment:1 Changed 6 years ago by lrbabe

Oops, this is an enhancement, not a bug sorry. I wish I could fix that by myself.

comment:2 Changed 6 years ago by lrbabe

And here is the pull request: https://github.com/jquery/jquery/pull/216

comment:3 Changed 6 years ago by jitter

  • Component changed from unfiled to effects
  • Priority changed from undecided to low
  • Type changed from bug to enhancement

comment:4 Changed 6 years ago by snover

  • Milestone 1.next deleted
  • Status changed from new to open

It’s a very good idea, but probably best implemented in the future when production browser actually support (it instead of only pre-release ones since it could be subject to change) :)

comment:5 Changed 6 years ago by lrbabe

As I said in the pull request, there's absolutely no need to hurry in merging this patch. I wrote it because I had a good idea of how it good fit into jQuery code and I wanted to do some tests.

Of course, merging it doesn't make sense before Firefox4 and Chrome10 are officially out :-)

comment:6 Changed 6 years ago by Daniel Lopez

Firefox 4 and Chrome 10 are officially out :D

comment:7 Changed 6 years ago by ajpiano

  • Milestone set to 1.6
  • Owner set to jaubourg
  • Priority changed from low to blocker
  • Status changed from open to assigned

comment:8 Changed 6 years ago by ajpiano

  • Owner changed from jaubourg to timmywil

comment:9 Changed 6 years ago by ajpiano

  • Cc jaubourg added

comment:11 Changed 6 years ago by john

  • Resolution set to fixed
  • Status changed from assigned to closed


Note: See TracTickets for help on using tickets.