Or, if Firefox doesn't quite do it for you (it almost was enough for me but not quite), then try MyIE2. I've seen the problem in IE you described but haven't had it happen since I started using MyIE2. It may be because MyIE2 doesn't have that bug, or it could be because I've got it programmed to clear my cache (but not my cookies) each time I exit it, so my cache never gets too messy for the bug to appear.