Skip to main content

Bug Tracker

Side navigation

#260 closed bug (fixed)

Opened October 09, 2006 06:16PM UTC

Closed March 15, 2007 05:17PM UTC

Last modified August 06, 2009 10:43AM UTC

Multiple simultaneous animations not completing in FF

Reported by: John Daharsh Owned by:
Priority: critical Milestone: 1.1.3
Component: effects Version: 1.1.2
Keywords: Cc:
Blocked by: Blocking:

Here is a demo:

4 divs moving simultanously on page load. In IE, it works beautifully for me. Firefox runs horribly and doesn't always complete the animations. (Win XP PRO SP2 - 2Ghz Proc, 1 Gb RAM)

Brandon Aaron saw that the animation did not complete in JQuery, John Resig also saw this and suggested that I throw it in Bug Tracker.

This was posted in the forums first.

Attachments (0)
Change History (6)

Changed October 10, 2006 06:08PM UTC by brandon comment:1

I've also had issues with animations not completeing ... even simple single div animations.

Changed October 16, 2006 05:12PM UTC by rsoule comment:2

I've had issues as well. Mine happen when positioning an element using the animate function. It doesn't seem to be position the x coordinates correctly. I guess different results every time.

Thanks John, you're the man.

Changed November 17, 2006 08:22PM UTC by john comment:3

milestone: → 1.1
priority: majorcritical
version: → 1.1

Changed January 11, 2007 05:25PM UTC by john comment:4

milestone: 1.1a
version: 1.1a

We're going to be tackling a retooling of the fx module for the 1.2 release - won't be able to get it in for 1.1.

Changed January 11, 2007 05:27PM UTC by brandon comment:5

component: corefx

Stefan came up with an idea for a rework of the fx engine and I believe it will fix this problem. Currently each animation (height, width, opacity, etc) all have their separate timers, even if they are all being animated at the same time. His idea is to only use one timer if it is all happening at once. This proposal was brought up on the dev list.

Changed March 15, 2007 05:17PM UTC by john comment:6

milestone: → 1.1.3
resolution: → fixed
status: newclosed
version: → 1.1.2

This should be fixed in SVN rev [1531].