First of all I wouldn't hit that bug because I don't like the CGI form-field methods. I'm not alone.

But let me give an example of one of those "IE JavaScript bugs" that you mention. And how to work around it.

I was doing some moderately sophisticated JavaScript stuff (couple of form elements interacting with each other) and created closures that referred the page form, and then assigned them as actions on form elements. IE would run slowly, take tons of memory, and then crash. I could not reproduce the problem on Mozilla.

The problem turned out to be that both IE and JavaScript use true memory managers, but different ones. So when cleaning up JavaScript, anything that is referred to by native widgets is not cleaned up. And when cleaning up native widgets, anything that is referred to by JavaScript is not cleaned up. I, of course, had a cycle with native widgets referring to JavaScript that referred back to the form that those widgets were on. Neither memory manager would clean that up, so the page would leak. After some active use, well you see the problem.

The work-around is to never have a variable referred to within a function refer directly to a native form widget. Instead remember widgets by name, and dynamically look them up in the form each and every time. That or convince people to not use Internet Explorer. :-/