Ticket #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: | ||
| Blocking: | Blocked by: |
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
comment:1 follow-up: ↓ 2 Changed 2 years ago by ajpiano
- Status changed from new to open
- Component changed from unfiled to effects
comment:2 in reply to: ↑ 1 Changed 2 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
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
This is addressing a similar problem to 6281 but with a different, probably more-user-friendly approach...can you file a pull req?