From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010208 BuildID: 2001020804 I think the summary says it all. Reproducible: Always Steps to Reproduce: Open the JavaScript Console and clear any messages there. Load the test case and click the text. Actual Results: The browser attempts to go to a nonexistent page. The JavaScript console shows an uncaught invalid pointer exception, with no source file, and line and column = 0. Expected Results: The attempt to go to a nonexistent page is expected.(Real code would prevent the default action, of course.) The console message is not expected. This is a regression since 20010125.

How completely creepy. It works for me now, both when I run it from Bugzilla, and when I run it from my local server. Maybe when Bugzilla spawned a new window for me it changed some state...I've since restarted Mozilla. This clearly is not as reproducible as I thought. I'll comment if it shows up again.

reassigning

I dont know if this is related, but in hotmail, when you select messages and press the delete button javascript errors are generated.

I'm seeing this again periodically this morning. I'll see if I can generate a reliable test case.

I can reproduce this consistently with the following steps. 1) Shut down Mozilla if it's running. 2) Launch Mozilla. 3) Open the JavaScript console and clear any messages. 4) Load http://bugzilla.mozilla.org/showattachment.cgi?attach_id=24916 (the test case). 5) Create a new browser window (Ctrl-N on Windows, Command-N on Macintosh). 6) Close the new window. 7) Click the text in the document in the original window. At this point, you should see the NS_ERROR_INVALID_POINTER message in the JS console. I can't see the whole message under Windows, but on the Mac, it indicates that the location of the error is line 12 of the test case, which the the form submit() call. Reproducible with Windows build 2001020804 and Macintosh build 2001020208.

Confirmed that this is a regression since 20010125. (Since I didn't fully understand how to reproduce the problem when I filed the original report, my claim that it was a regression was suspect.)

Probably the same problem as bug 68321.

I agree, this sounds like a dup of bug 68321. *** This bug has been marked as a duplicate of 68321 ***

Verified dup.