The gallery itself is breaking w3c valid html which appears to be causing the problems on my system at least (thumbnails not becoming clickable).
-
Line 170, Column 38: required attribute "src" not specified.<li style="visibility:hidden;"><a><img></a></li> ✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
-
Line 170, Column 38: required attribute "alt" not specified.<li style="visibility:hidden;"><a><img></a></li> ✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
-
Line 170, Column 42: end tag for "img" omitted, but OMITTAG NO was specified.<li style="visibility:hidden;"><a><img></a></li> ✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Those in particular are AFTER the thumbnails though, which confuses me. Theres no reason they're there for one, but ignoring that those shouldn't be causing problems with the rest of the thumbnails.
Theres a bunch of XML failures near the end though which might be causing the problem.
http://validator.w3.org/check?uri=h...matically)&fbc=1&doctype=Inline&fbd=1&group=0
If you can, get the errors fixed and see if the problem stops appearing in Firefox. IE's usually more lax as far as enforcing the standards go, so theres a good chance it's simply ignoring the errors and rendering it how it THINKS it's supposed to look. Firefox on the other hand tends to render it exactly as it's coded, and when theres errors, it doesn't bother fixing them - it figures you coded it how you wanted it to show up...
Hang tight for other user opinions on this though; I'm not entirely positive fixing those errors WILL fix the problem, but it's not a bad place to start in any case.