Closed
Bug 190876
Opened 21 years ago
Closed 15 years ago
disabled form elements kill dom events
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
RESOLVED
DUPLICATE
of bug 218093
People
(Reporter: phoyt, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 As seen in the testcase (click on any text field), a disabled form element will kill onclick events in disabled form elements regardless of whether the event belongs to the element itself, or whether the event belongs to a container div. This applies to onMouseover events equally. Reading the w3c html spec, it doesn't look to me like this is the intention of disabled elements. I believe that only their usefulness as elements of the form is to be disabled, not their ability to handle events at all. Reproducible: Always Steps to Reproduce: 1. Open the URL above. 2. Click on each text field Actual Results: The non-disabled text fields will produce alerts when clicked upon. The disabled ones will not. In Internet Explorer, only the second disabled element will produce an alert -- the second row has the onclick event in the container while the first has it in the element itself. Expected Results: I expected Mozilla to behave like Internet Explorer. Also, I think it would be preferable if all form elements on the test case produced onclick events.
![]() |
||
Updated•21 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
Comment 1•18 years ago
|
||
Possible Dup of 218093?
Comment 2•18 years ago
|
||
*** Bug 330368 has been marked as a duplicate of this bug. ***
Comment 3•17 years ago
|
||
*** Bug 347537 has been marked as a duplicate of this bug. ***
Comment 4•17 years ago
|
||
*** Bug 347537 has been marked as a duplicate of this bug. ***
Updated•15 years ago
|
Assignee: saari → nobody
QA Contact: vladimire → events
Comment 6•15 years ago
|
||
Duping to bug 218093 as there's more information/testcase etc.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•