Skip to main content

Bug Tracker

Side navigation

#9435 closed bug (cantfix)

Opened May 26, 2011 07:29PM UTC

Closed June 02, 2011 06:27AM UTC

javascript error while reloading during animation

Reported by: JorisDebonnet Owned by: JorisDebonnet
Priority: low Milestone:
Component: effects Version: git
Keywords: Cc:
Blocked by: Blocking:

It's really nothing serious, but something very slightly goes wrong, so I thought I'd just report it.

When you reload a page that is currently doing an animation, you get a javascript error. Probably because jQuery is still trying to reference something for the animation that has disappeared in the meanwhile.

Since the 'reloaded' page works as it should, it's certainly not a big thing. Only that I get red messages in some addons that are tracking errors.

It may be easy to fix though, although I'm not sure whether it would cause any performance issues (if an additional check is required on every step).

The 'error' happens on current line 8400, where it merely says:

   if ( timerId )
Attachments (0)
Change History (7)

Changed May 26, 2011 07:37PM UTC by rwaldron comment:1

component: unfiledeffects
owner: → JorisDebonnet
status: newpending

I see an illegal invocation error caused by your setTimeout trying to execute location.reload

Changed May 26, 2011 07:39PM UTC by rwaldron comment:2

Is this in a particular browser? I've tested all of them after removing your setTimeout and I see no errors.

Changed May 26, 2011 07:42PM UTC by JorisDebonnet comment:3

status: pendingnew

Do you reload the page though?

Here's a slightly changed version where you can reload by clicking the button (but you can of course just reload the page/frame yourself):

I see the errors appear in Firebug and in Webdeveloper Toolbar, in Firefox 4.

Changed May 26, 2011 07:44PM UTC by JorisDebonnet comment:4

The error is: "attempt to run compile-and-go script on a cleared scope".

Changed June 01, 2011 05:40PM UTC by dmethvin comment:5

status: newpending

I've verified this, but it looks like a bug in Firefox to me. Seems like FF must not be stopping the timer. It's beyond our abilities to control I would think. Can you report it to Mozilla?

Changed June 01, 2011 10:30PM UTC by JorisDebonnet comment:6

status: pendingnew

You probably have a point. I have reported it as a Firefox bug right here:

Let's see what they say :)

Changed June 02, 2011 06:27AM UTC by addyosmani comment:7

priority: undecidedlow
resolution: → cantfix
status: newclosed

As this is an issue with Firefox itself and is currently beyond the scope of our ability to fix, the ticket is being closed as cantfix. Should we however discover at a later point that there is a core patch that can be applied to fix the behaviour experienced, please feel free to re-open.