Side navigation
#7917 closed feature (fixed)
Opened January 07, 2011 03:01AM UTC
Closed April 12, 2011 04:34AM UTC
Last modified March 17, 2012 08:41PM UTC
.animate() when used with large groups of elements is not "in sync"
Reported by: | gnarf | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 1.6 |
Component: | effects | Version: | 1.4.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Brought up by polyrhythmic in IRC - and also here: http://www.splashnology.com/blog/jquery/237.html
A simple test case : http://jsfiddle.net/gnarf/GfUZf/
The internal jQuery.fx.custom() assigns jQuery.now() to each elements animation as its startTime, which as the ms add up to calculate start/end positions, creates a "drifting" effect on the large animation.
https://github.com/gnarf37/jquery/commits/animate_fix proposes one solution to this - allowing (and defaulting to) a synchronized startTime that gets passed down the line via the "speed" object (which becomes this.options in the .fx)
Attachments (0)
Change History (4)
Changed January 07, 2011 03:04PM UTC by comment:1
component: | unfiled → effects |
---|---|
status: | new → open |
Changed January 07, 2011 10:49PM UTC by comment:2
Replying to [comment:1 ajpiano]:
This is addressing a similar problem to 6281 but with a different, probably more-user-friendly approach...can you file a pull req?
Your wish is my command: https://github.com/jquery/jquery/pull/167
Changed January 10, 2011 12:56AM UTC by comment:3
milestone: | 1.next → 1.6 |
---|---|
priority: | undecided → blocker |
I’m going to schedule this for an early release in 1.6 branch.
Changed April 12, 2011 04:34AM UTC by comment:4
resolution: | → fixed |
---|---|
status: | open → closed |
This has been landed.
This is addressing a similar problem to 6281 but with a different, probably more-user-friendly approach...can you file a pull req?