- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1 and 9 items
- Europe
- Exclusive Author
- Has been a member for 2-3 years
- Item was Featured
- Referred between 100 and 199 users
hello. we are just starting with jquery and have some serious problem with firefox. every other browser, even ie9, renders better, and not chopped like firefox. firefox with hardware acceleration turned on is rendaring poorly, but with hardware acceleration turned off is just fine. any ideas? ps. just a left right animation with jquery easing plugin.
I usually get that when Firefox goes over ~500k of memory consumption. Does it run smooth when you just open Firefox and have only that tab open?
Oh, and… some code? 
- Author had a File in an Envato Bundle
- Sold between 250 000 and 1 000 000 dollars
- Author was Featured
- Item was Featured
- Contributed a Tutorial to a Tuts+ Site
- Exclusive Author
- Has been a member for 3-4 years
- India
Most possibly due to CSS3 effects. Like, box shadows on big block elements or a large number of elements using the box shadow using CSS3 .
A link would help 
Hmmm, works smooth for me in both Firefox 4 and Chrome latest…
Again, could you take a look at Firefox’s load in Task Manager?
P.S.: I have hardware acceleration turned off in Firefox.
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1 and 9 items
- Europe
- Exclusive Author
- Has been a member for 2-3 years
- Item was Featured
- Referred between 100 and 199 users
digitalimpact saidTurn it on and see the baby go. That is the problem. It’s default on so customers will see it choppy.
Hmmm, works smooth for me in both Firefox 4 and Chrome latest…Again, could you take a look at Firefox’s load in Task Manager?
P.S.: I have hardware acceleration turned off in Firefox.
duotive said
Turn it on and see the baby go. That is the problem. It’s default on so customers will see it choppy.
Crap…
Another one to add to my Firefox hate list.
Anyway, a few things I’d try:
- use latest jQuery (1.6)
- use for() instead of $.each()
- use IDs instead of classes, since jQuery uses the native getElementByID() method (faster queries)
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1 and 9 items
- Europe
- Exclusive Author
- Has been a member for 2-3 years
- Item was Featured
- Referred between 100 and 199 users
digitalimpact said
duotive said
Turn it on and see the baby go. That is the problem. It’s default on so customers will see it choppy.Crap…
Another one to add to my Firefox hate list.
Anyway, a few things I’d try:
- use latest jQuery (1.6)
- use for() instead of $.each()
- use IDs instead of classes, since jQuery uses the native getElementByID() method (faster queries)
Thanks for the ideas. We wanted to use classes for multiple instances. But this is an easing problem not something to do with the element creation.
duotive said
But this is an easing problem not something to do with the element creation.
...easing problem which is, in the end, handled by… jQuery 
You could try and log them with console.time() and see if any of the last 2 ideas impact your script 
- Author had a File in an Envato Bundle
- Author was Featured
- Bought between 1 and 9 items
- Europe
- Exclusive Author
- Has been a member for 2-3 years
- Item was Featured
- Referred between 100 and 199 users
digitalimpact saidYou know what is the funny thing? Mootools has no problems!!
duotive said
But this is an easing problem not something to do with the element creation....easing problem which is, in the end, handled by… jQuery
You could try and log them with console.time() and see if any of the last 2 ideas impact your script![]()
