Closed
Bug 345545
Opened 18 years ago
Closed 18 years ago
window.close() crash in onreadystatechange after onsubmit
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 281139
People
(Reporter: bugs, Unassigned)
References
()
Details
(Keywords: crash, testcase)
Attachments
(1 file)
917 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060410 Firefox/1.0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
window.close() causes the browser to crash if called from within an onreadystatechange handler for an XMLHttpRequest object that was used in an onsubmit handler for a form.
Reproducible: Always
Steps to Reproduce:
1. Click the "Launch Demonstration" link to open the demonstration in a Javascript popup window.
2. Click the Submit button in the new window
3. Click the OK button in the Javascript alert.
4. The browser should crash. If it doesn't, try pressing the tab button.
Actual Results:
Browser crashes.
Expected Results:
Should have closed the popup window.
Tested under a clean install (default prefs, no extensions or themes).
Also reproduced under Windows 2000: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Must be run in a popup window, because it uses window.close()
It doesn't matter what you request with the XMLHttpRequest object.
See the attached testcase, or the online testcase at the specified URL.
Must be run in javascript popup, since it uses window.close()
See the bug's URL for an online testcase which opens a popup for you.
Comment 2•18 years ago
|
||
Thanks for the report (and great testcase), Andrew. Fortunately, this crash will be fixed in Firefox 1.5.0.5.
Comment 3•18 years ago
|
||
*** This bug has been marked as a duplicate of 281139 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•