Any HTML gurus out there care to take a stab at why this page acts strangely with Internet Explorer 6?
The left-side menu gets truncated more often than not - on a slow connection / slow PC, I can see the menu appear properly next to the pictures, then that group of four pictures kicks over to the left. Hitting F5 or refresh almost always moves the pictures off the menu.
It’s just fine with Firefox or Safari.
Can you reliably reproduce the problem, somehow? I don’t have a slow enough connection to see it myself. I tried to slow down my regular one by downloading something in the background, but the page still looked fine every time I went to it (in IE6).
I can repeat it all day long. Even stranger, if I scroll down on the page, the part that disappears off the top of the window will be truncated when I scroll back up - effectively truncating only the top half or so of the menu.
I dunno who put it there, but there’s a comment tag in the source referring to a bug in IE 6 and re-sizing. Apparently, this is the bug.
Without going into an awful lot of detailed looking, there is an ONLOAD on the table that contains the pictures. I don’t think that’s valid.
Anyway, the images get loaded and then the script tries to pre-load other images for the mouseover effect using the ONLOAD on the table.
So it looks like the HTML is actually malformed and causes the images to load in the wrong place.
When you refresh the page, the images are already cached, so they don’t have to be loaded again and will appear in the right place as defined by the javascript.
The designer would be better off avoiding this scenario by setting proper attributes and values and not relying on the images themselves to set the widths of the cells so the images “fit”.
They should put the ONLOAD into the BODY statement too.
Woah. All that code just to get the letters to change colour.
I suggest that page should not use clumsy javascript for the mouseover, and either not have any mouseover at all, or use CSS to change the background of a blank image instead. It’d be faster, and mean cleaner code. And would work in every browser properly.
Don’t know if that would fix the problem, though.