I wonder why, but for some reason FF and IE call testZip() and testEmail() with the params fine. They both call writeTo() and writeTo() does update the div.innerHTML even when I had the BR tag with the < and when I replaced it with &lt; it still updated it. testEmail() and checkPass() which are after the writeTo() function should have the same problem of testForm() because they came after the writeTo() function as well, but only testForm() doesnt respond. I dont understand why the other buttons that pass params work, but the one function that doesnt pass any params from the button doesn't. Even checkPass() wich passes params to the isPassword() internally works. But testForm(), which would call all three functions, does not, while it also passess params internally. Even with the parameter passing being wierd, why would the other two functions that receive params from the onclick work and the checkPass() function that has two params coded into it would work and not the testForm. Have you tried the code in a browser? I have tested it in FF2 and IE6 and both behave the same. Run the three buttons and don't respond on the "check" button. How would you suggest I write the code so that this doesn't happen?

The fact that a browser will interpret wrong code "the way I meant it to work" does not mean that other browsers will do so, nor does it mean that the browser will continue to do so in the future.