Regardless, I am quite happy to have found the info at search-this and SitePoint. The forums at SitePoint are a goldmine.

Well nothing surprises me with IE as it always seems to have one more bug to catch you out.

Usually clearing the cache means clearing the history and deleting the temporary internet files also, so make sure you have done both. A corrupted image in the cache or a full cache will cause the same problems as the “every visit” option. Also make sure you have a reasonable amount of space set aside for the temp internet files and the slider isn’t set at zero.

Other than that I can’t think what else could be causing it apart from a corrupt Internet Explorer of course but there’s not much you can do about that and isn’t worth the risk of re-installing. If everything else seems ok then I wouldnt upset anything else.

If you have a very slow (or old) machine the the hourglass will be visible more easily but in faster machines its a very quick flicker (unless the images are very large) and as I said before its hardly visible on my machine. It’s a shame that here is no simple way to turn it off completely.

Sorry I can’t think of anything more constructive.

@paul

Strangely enough, I am still getting the hourglass flicker with my settings on automatic, but only me. No one else in my office who is set to automatic has the problem. I cleared my cache, close IE down, everything I could think of. I even tried some of the .htaccess tricks in that article.

Any idea why this might still happen on Automatic? When I set it to everytime I get the bad flickering, but on Automatic I only get the hourglass.

Thanks.

Thanks Jiun for stopping bye and saying something!

cheers,
mark

Thanks a lot for the update, it’s really great. I noticed that before the update on horizontal links the link tended to extend below the actual image (I posted this as a comment before I think), now the problem is gone! In the interest of learning (I am a newbie at CSS) I was wondering if you could point out where the problem was exactly and how you solved it?

Thanks!

Actually, that is good news. Looking at my sample page from home tonight, I didn’t have the problem at all. I had actually seen comments in some of you guys’ threads about some of these problems being ‘developer only’ issues, because we tend to change our cache settings. I just hadn’t realized I was getting caught by it myself in this case.

So, anyway, since our client base is actually encouraged to use the default settings this will work for me. For the few who don’t and decide to complain, at least I have an acceptable solution for them.

My boss tried for days to work around this issue on a personal project he was working on. He was using the single sliding image method. He’s going to feel as dumb as I do when I tell him.

Thanks!