Closed (fixed)
Project:
Couloir Slideshow
Version:
5.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
25 Sep 2007 at 03:59 UTC
Updated:
18 Aug 2008 at 12:00 UTC
Jump to comment: Most recent file
First: Congratulation. The module was up and running within minutes.
A bug seems to be somewhere when this module is used in conjunction with the standard Garland theme. It works fine in Firefox but in IE6 positioning and styles get messed up when the slideshow block is part of the page.
I guess it's rather a JS than CSS problem.
Thanks for investigating.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | couloir_slideshow_scale_debug.png | 104.94 KB | chirale |
Comments
Comment #1
chirale commentedI've experienced the same layout issue, even in IE 7. Things going right in Firefox 2, Konqueror 3, Opera 9, Safari 3.
In IE, all contents collapse in a single central column when the slideshow box load the first image of the set.
Comment #2
chirale commentedProblem is somewhere inside the Effect.Parallel call (resizeOutBox function) on js/slideshow.js.
If you comment Effect.Parallel, layout isn't more messed up in IE, but the box remain unscaled. Anyone knows what going wrong when IE run this piece of code?
I attach a screenshot of the result when Effect.Parallel call is commented.
UPDATE:
Error occurs only when Effect.Scale is applied to photoBox.
Comment #3
meichr commentedI had the same problem with IE6 and IE7.
The reason seems to be that within the block a class with the name "Container" is used which is also used within the Garland theme, and possibly other themes (ATCK, etc.).
The class name "Container" has to be changed to a unique class name, e.g. "PhotoContainer" as in the following code examples.
There are several files in which the class name needs to be changed to make the module also working under these themes for IE6 & IE7.
1. couloir_slidewshow.module
Instead of
write
2. js/slideshow.js
Instead of
write
3. css/couloir.css
Instead of
write
Hope this helps,
Christian.
Comment #4
ComputerWolf commentedI have applied the changes made by Christian to version 5.x-1.3 and the module now works properly with previously conflicting themes, specifically Garland.
Comment #5
ComputerWolf commentedComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
seutje commentedthis is exactly why I make all my CSS IDs strictly unique to the specific theme
like if I would of made a theme named Garland, every ID would have Garland at the end
so container would become containerGarland
makes it a lot easier for me to separate theme IDs with module IDs or w/e