Doesn't the IE javascript error popup have a checkbox 'display on error'?  Simply uncheck this, and the javascript errors appear only as a yellow warning sign in the bottom left.  I'm using IE 7, and my code is riddled with javascript errors, but Selenium tests run very well.

Has anyone found a solution to this problem yet?  I get permission denied problems using *iexplore so I switched to *iehta but now I get script error popups.  How can these be suppressed?

This is a complete frustration. I spent way too much time building an entire framework based on Selenium Grid + Selenium RC where the purpose is to run all the functional tests against multiple environment configurations. It works perfectly fine with FF2 and FF3, but the scripts running against IEx crap out 50% of the time stalling the entire test suite. I am about to give up on Selenium because of this. It is just not stable enough for a real world application.

Does anyone have a solution for the IEx JavaScript crashes?

Yes, I have exactly the same problem.  Spent months developing a framework to run Selenium tests on multiple configurations.  Now I find that iehta Javascript error popups have effectively blown the whole thing out of the water.  Is there still no solution for this?

Well on second thought, of course, this is not a solution.  Yes, it suppresses the popup window, but at the cost of breaking everything else that depends upon running js.

Really, the problem is not with Selenium, which is correctly reporting an error.  The answer is that your site has real errors in the js.  If engineering decides that they will not fix these errors, then that's an end of it.  You cannot use Selenium to navigate a site that is simply broken.  This is the price you pay for a tool that, unlike, say, WebTest, uses the real browser.  And ironically, it is used as THE selling point for Selenium over Webtest: "Oh no .. we have to have something that runs in the real browser, so we can see errors that real users experience."  OK.  Here are your real errors.  If eng is not going to fix them anyway, then the anti-WebTest stuff is empty rhetoric.