Closed Bug 99628 Opened 23 years ago Closed 23 years ago

Javascript causes mozilla to crash when it completes its function.

Categories

(Core :: JavaScript Engine, defect)

x86
Windows NT
defect
Not set
normal

Tracking

()

CLOSED WORKSFORME

People

(Reporter: daniel, Assigned: rogerl)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 BuildID: 200108110 A javascript on this form page crashes Mozilla every time. I've tested it in Netscape 6.1 and it doesn't seem to have the problem. The script is found at the "Problem Description" part of the form. The script is supposed to just tally the number of characters used and then warn the person when you have reached 300. Just clicking inside of the field will eventually give crash your systme. This leads me to believe that Mozilla has a problem handling the function associated with the onFocus. Reproducible: Always Steps to Reproduce: 1. Go to the URL: http://www.washburn.edu/its/docs/forms/PurchaseForm.htm 2.Place curser inside the text box below "Problem Description" 3.Should crash browser after about 10 or 15 seconds, with or without typing Actual Results: Just placing the curser inside the text box for "Problem Description" crashes Mozilla Expected Results: The script should just calculate the number of characters inside the one text field
Worksforme (apart from the crappy design of the script that makes it eat up CPU like mad) current linux cvs build. Daniel, could you please try a recent build? Yours is pretty old...
WFM Win2k 20010912
No problems using Mozilla trunk and 0.9.4-branch binaries 2001-09-10 WinNT. Marking WORKSFORME -
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Marking Verified - daniel@ztiger.com: could you try a current build and see if the problem still occurs for you? If so, please reopen this bug; thanks -
Status: RESOLVED → VERIFIED
Javascript problem is solved by using the win32 0.9.4+ build.
Status: VERIFIED → CLOSED
You need to log in before you can comment on or make changes to this bug.