Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Javascript Timing Queue in Firefox only

  • 1 reply
  • 1 has this problem
  • 3 views
  • Last reply by cor-el

more options

Hello ,

I am recently encountering problems on Firefox with setInterval and setTimeout functions. It seams that when you have for example slideshow or carousel running on the page and you switch on some other tab, there are some errors in javascript animation. It looks like it kinda queues all animations and when you switch focus to that tab again, then it does them very quickly , ruining slideshow or carousel with very fast animations. On chrome , IE, Safari it all works well, I just encountered this problems from Firefox 4+.

Thanks on your help.

p.s. Maybe it is my error in javascript, but it worked well before and it works well in other browsers.

Hello , I am recently encountering problems on Firefox with setInterval and setTimeout functions. It seams that when you have for example slideshow or carousel running on the page and you switch on some other tab, there are some errors in javascript animation. It looks like it kinda queues all animations and when you switch focus to that tab again, then it does them very quickly , ruining slideshow or carousel with very fast animations. On chrome , IE, Safari it all works well, I just encountered this problems from Firefox 4+. Thanks on your help. p.s. Maybe it is my error in javascript, but it worked well before and it works well in other browsers.

All Replies (1)