https://github.com/brantburnett/jquery.smoothanim
jQuery Smooth Animations using Firefox 4 mozRequestAnimationFrame
https://github.com/brantburnett/jquery.smoothanim
Last synced: 3 months ago
JSON representation
jQuery Smooth Animations using Firefox 4 mozRequestAnimationFrame
- Host: GitHub
- URL: https://github.com/brantburnett/jquery.smoothanim
- Owner: brantburnett
- Created: 2010-10-24T17:56:27.000Z (over 14 years ago)
- Default Branch: master
- Last Pushed: 2010-10-24T17:57:29.000Z (over 14 years ago)
- Last Synced: 2025-01-14T10:18:12.812Z (5 months ago)
- Language: JavaScript
- Homepage:
- Size: 89.8 KB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.txt
Awesome Lists containing this project
README
jQuery Smooth Animations
Author: Brant Burnett
http://btburnett.com
http://twitter.com/btburnett3
Compatibility: Tested with jQuery 1.4.3 only
Overview
---------
jQuery Smooth Animations is an experiment in utilizing the new, proposed animation API found in Firefox 4.
It should be noted that this
API is just a proposal and is experimental. Using it on live websites isn't recommended until the API
is finalized.
The jQuery Smooth Animations works by replacing parts of the standard jQuery API to make use of the new
animation API if it is available. It should still be fully compatible with browsers that don't implement
the animation API.
The end result of this plugin is that animations run more smoothly on Firefox 4, by syncing the animations
with paint events. In my experimental comparisons between Firefox 4 Beta 6 and Firefox 3.6.12, I noticed
a significant improvement in the jerkiness of the animation in the example.
I recognize that this plugin could be slightly less invasive by not replacing any of the API if
window.mozRequestAnimationFrame is not found. However, I wanted to demonstrate how the code could function
within the jQuery library itself rather than as a plugin. This is based on the theory that at some point,
once the API is standardized, support will be integrated into the jQuery library.
Integration into the library would also allow us to eliminate the override of jQuery.now, instead using
smarter logic within jQuery.fx.step. I simply didn't want to replace jQuery.fx.step because of the extensive
logic it contains which could be changed in future releases of jQuery.