Closed
Bug 203881
Opened 22 years ago
Closed 22 years ago
Browser crashes on <select name="lightm_db" onchange="this.form.submit()"> code
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: t.rother, Unassigned)
References
()
Details
(Keywords: crash, stackwanted, Whiteboard: TB19642238E)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030429
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030429
If you click on the pulldown menu inside phpMyADMIN application (a web interface
for mysql), Mozilla crashes.
Reproducible: Always
Steps to Reproduce:
1. use an installation of phpMyADMIN (this is mostly internal used, so I can not
give you a public URL for this)
2. on the startup page, a list of available databases ist shown on the left frame
3. click on the pulldown window.
Actual Results:
Browser crashes. See talkback issue TB19642238E
Expected Results:
Pulldown is shown
This is a persistent issue for the nigthlies since 1 or 2 weeks. I would think
is has to to with the "this.form.submit()" event. See page code enclosed.
| Reporter | ||
Comment 1•22 years ago
|
||
Code for navigation page with <select name="lightm_db"
onchange="this.form.submit()"> section which may be the reason for the crash.
See www.phpmyadmin.net for more details.
| Reporter | ||
Updated•22 years ago
|
Attachment #122079 -
Attachment description: phpmyadmin page code → page code - html output
Comment 2•22 years ago
|
||
-> DOM Level 0
Assignee: rogerl → dom_bugs
Component: JavaScript Engine → DOM Level 0
Keywords: crash,
stackwanted
QA Contact: pschwartau → ashishbhatt
Whiteboard: TB19642238E
| Reporter | ||
Comment 3•22 years ago
|
||
This is the original php code from which the html output is generated
| Reporter | ||
Comment 4•22 years ago
|
||
As of build 20030502, this seems to be fixed now. But I still see a crash on a
js-enhanced page. Will file that separately ...
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•