Does it really crash IE6?
Anyway, seeing as IE6 has a 7-ish% and declining market share, do you really need to care about those users? There may be a value to doing so, but there is certainly a cost involved. When we still had support for IE6, I probably spent about 30% of my client-side development time just making things work in IE6.
Another very easy option is to simply provide IE6 users with a non js form.
Third way is to start debugging. Add output code to see just how far you get before IE6 breaks. Or if it doesn't work at all, start disabling parts of code until you have a minimal non-breaking code, and then enable parts again until you have minimal non-working code.
Add if checks for pretty much every function you use
if (document.getElementById) {
// function exists
}
else {
alert('getElementById is missing');
}
Just an example, since this one does exist in IE6 as well. But once you find functions that does not exist, or track down code that breaks in IE6, you can start googling on work-arounds.
Also, fun_login will not work unless you define it.