As a testament to how much I enjoy this site, I tried using Firefox as my primary browser. Unfortunately, it doesn't work at all with the web version of Outlook - surprise, microsoft's webmail product only supports their own browser. It also doesn't give me some cute little mouseovers at Yahoo, but the real issue is that I can't use my work mail at all through Firefox. And I am unwilling to use IE here because windows pop-up on me at rates that make my head spin whether I move the mouse or not and I am frequently scrambling to close them. So, now I am left using two different browsers - one for this site and one for everything else. That really isn't an effective solution.

I don't know what was implemented that causes this problem, but it isn't working and it is causing far more harm than good. I would therefore add to the list of fixes that you roll back to the earlier version and remove the offending code until your third party provider can get it fixed. Forcing everyone to suffer through bad code (to spec or not, surely any reasonable tester should confirm something works with the browser that has > 80% market share) for more than a few days just doesn't seem like the right answer to me.

By the way, everything seems back to normal and the site has been working great lately. I am assuming a fix has been discovered and applied. Thanks!

I don't think so. I am continuing to experience the same problem when pages are loading in IE. If you happen to touch one of the top menu/drop-down items with the cursor during page loading, the page stops loading and responds with an error message. Hitting the Refresh (F5) button does reload the page. This is the only site that I have experienced this problem on. I understand John@FT's prior comment about not moving the mouse while the page is loading, and some people may be that patient just to pause and wait, but I often know that I will be scrolling down as soon as the page loads. Moving the mouse over to the scroll bar as the page is loading is when the error often occurs for me. (Not to suggest that the destination of the cursor is the problem, only the movement of the cursor over a "sensitive area.")

No, it hasn't been fixed and yes, it's still irritating especially when I'm trying to post something.