Closed (fixed)
Project:
jCarousel
Version:
6.x-2.6
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Dec 2011 at 18:33 UTC
Updated:
24 Dec 2012 at 08:21 UTC
I have the following settings in Views
Basic Settings
- Use AJAX: true
- Items to Display: 6
jCarousel settings:
- Number of Visible Items: Auto
- Scroll: 6
- AJAX load pages: true
In Firefox everything works as expected. You scroll back and forth through the carousel. In Safari, however, when I scroll through the carousel it begins to break the design. The jCarousel begins to load in extra rows as you scroll. (See attached screenshots for a peek). I have hard coded height for the container and clip in my CSS to no avail (in Safari).
Setting Views as follows corrects this.
Basic Settings
- Use AJAX: false
- Items to Display: Unlimited
jCarousel settings:
- Number of Visible Items: Auto
- Scroll: 6
- AJAX load pages: false
Is this expected or a bug? thanks
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 3.png | 605.83 KB | babycourageous | |
| Picture 2.png | 483.66 KB | babycourageous |
Comments
Comment #1
mattschlanger commentedI am seeing a similar problem on safari, both on the mac and iPads, but not on PC. Chrome, Firefox and IE are all fine. The jCarousel window starts to load in two rows, increases it's height, empties after showing all items once, while staying at the larger height. Using circular wrap content seems to be the issue, though it's the best setting visually when it's working. The above settings with circular does not fix the problem. I had to set circular to "both". I have css settings for .jcarousel-clip-vertical set to fixed height (same for horizontal). Has anyone figured out how to use circular on Safari? thanks.
Comment #2
chriso commentedI have been investigating this for a customer recently. I can confirm the same behaviour on Windows XP running Safari 5.0.1. I found the same as mattschlanger; the circular wrap is a reliable trigger.
The problem no longer occurs if Safari is updated to 5.1.5, which was released a week after the last comment above for both Windows and Mac. I also tested 5.1.7 on XP, and 6.0.2 on OS X.
As this issue hasn't had any further activity since March and it seems plausible that bug fixes within Safari itself since that time have resolved the issue, I'm going to mark this as fixed. Please test again and re-open if I've made an error.