I am using the bootstrap carousel in a test site and I cannot get it to run smoothly in Firefox. It works correctly in Chrome and IE.
The issue is not that its broke, and the first image loads as it should. The problem is when it transitions/slides to the second image, only half of it displays and then loads. The same thing when it transitions to the third image, only a third of the image appears to display, and then loads.
Has anyone encountered this in Firefox? (Version 35.0.1)
I personally haven’t experienced this. Do you have a website where we can test to see if we get the same behavior?
Yes.
I’m not seeing a problem there in Firefox 35 on Ubuntu Gnome 14.10.
Windows 7, Firefox 35.0.1. Not happening for me. Smooth as a babies buttocks.
That’s strange! I have tested on two different machines both running latest ff version, and it has the same result.
Could it be an add-on they both have in common causing the issue? (I have quite a few add-ons, and no problem with it, so I’m just guessing. )
No. Both of the machines have no FF add-ons. This one has really got me. 
Perhaps reinstall Firefox? Delete everything and get a fresh install?
I just tried that. Still the same.
If anyone is gonna have a jerky/flaky rendering of a JavaScript of jQuery product, it’s ME. But this one slides like skis on a slope… (a northern hemispherically seasonal way of saying “smoothly”).
You’re not the only one! We’ve seen similar issues with Firefox’s rendering of the Bootstrap carousel. I do not have a solution for this problem, though. 
Okay whew. That actually makes me feel better.
I guess the best solution is to not use bootstrap carousel in this case, unless a fix is created.
I am experiencing exactly the same problem with my carousel. Earlier this month I have found a bug report that covered this issue, and I stumbled upon your post while trying to find it again …
Someone stated that this bug will be fixed in the next update in early March …
Unfortunately I cannot find the page where I got this information from …
Found this bug report which seems to cover this issue. Should be fixed in v36 …
V36 fixed the issue.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.