#7917 closed feature (fixed)
.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)
Change History (4)
comment:1 follow-up: ↓ 2 Changed 6 years ago by ajpiano
- Component changed from unfiled to effects
- Status changed from new to open
comment:2 in reply to: ↑ 1 Changed 6 years ago by gnarf
Replying to 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
comment:3 Changed 6 years ago by snover
- Milestone changed from 1.next to 1.6
- Priority changed from undecided to blocker
I’m going to schedule this for an early release in 1.6 branch.
comment:4 Changed 5 years ago by john
- Resolution set to fixed
- Status changed from open to 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?