Okay, this is a first: Thickbox performs perfectly in IE, but displays way to the bottom left in Safari.

This is for a latest-and-greatest all around Drupal 6 install. Am I the first person to have this problem? Saw an issue that mentioned positioning in Safari having to do with Thickbox on the registration page, but haven't found anything else mentioning this. Tried to implement that patch but the code didn't match up.

Comments

frjo’s picture

frjo commented

Do you have a example site where we can see the problem?

I use Safari as my main browser and have not seen any problems with Thickbox.

drupup’s picture

drupup commented

Try this page:

http://www.ecovision360.com/listinggreenbusiness/green-guys-texas

The Photos are in a right sidebar block down the page. Click on them in any other browser, everything works correctly. Click on them in Safari, it's way down bottom left, off the screen.

drupup’s picture

drupup commented

Have you had a chance to check this out? This is only happening in Safari, but it's on both Mac and PC side. Might have something to do with the blocks/regions setup...it's rare that IE is fine and another browser is the problem.

frjo’s picture

frjo commented

I made a local cope of the page above and did some testing. When I added in the thickbox.css file manually after the other CSS with,

Thickbox works in Safari again.

I suspect that you have some CSS in your theme that overrides thickbox.css and Safari is a bit unhappy about that.

drupup’s picture

drupup commented

Okay, interesting...

I tacked the style descriptions from your .css file to the top of my style sheet, and now everything is working correctly, even though your styles are at the top, before any of the other styles. If this was a cascade issue, they should still be getting overruled. I think something about the optimization process for the module .css files is causing the problem. But only for this module, and only in Safari. Odd.

Anyway, this fixes it. Thanks. Love the module.

frjo’s picture

frjo commented
Category: bug » support
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.