Closed
Bug 366517
Opened 18 years ago
Closed 11 years ago
Mutation Events not fired in disabled form controls
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: joao.eiras, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(10 files)
768 bytes,
text/html
|
Details | |
756 bytes,
text/html
|
Details | |
765 bytes,
text/html
|
Details | |
853 bytes,
application/xhtml+xml
|
Details | |
881 bytes,
application/xhtml+xml
|
Details | |
792 bytes,
text/html
|
Details | |
804 bytes,
text/html
|
Details | |
778 bytes,
text/html
|
Details | |
795 bytes,
text/html
|
Details | |
816 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070109 Minefield/3.0a2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070109 Minefield/3.0a2pre
Mutation events aren't fired for disabled form controls like button, textarea, input and select.
Reproducible: Always
Reporter | ||
Comment 1•18 years ago
|
||
Reporter | ||
Comment 2•18 years ago
|
||
Reporter | ||
Comment 3•18 years ago
|
||
Reporter | ||
Comment 4•18 years ago
|
||
Reporter | ||
Comment 5•18 years ago
|
||
Reporter | ||
Comment 6•18 years ago
|
||
Reporter | ||
Comment 7•18 years ago
|
||
Reporter | ||
Comment 8•18 years ago
|
||
Reporter | ||
Comment 9•18 years ago
|
||
Reporter | ||
Comment 10•18 years ago
|
||
Testcase 1 - DOMAttrModified in button works the first time it's loaded. If you refresh it it'll fail.
![]() |
||
Comment 11•18 years ago
|
||
We should fix this for 1.9, imo. We have XXX comments about this already, and I don't really know why we're blocking these events. If it's a matter of preventing default actions for certain events (e.g. click), or even preventing propagation of said certain events, we should do that instead of nixing all events.
The affected classes are: nsHTMLInputElement, nsHTMLButtonElement, nsHTMLTextAreaElement, nsHTMLSelectElement.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: in-testsuite?
Flags: blocking1.9?
Keywords: testcase
OS: Windows XP → All
Hardware: PC → All
Reporter | ||
Comment 12•18 years ago
|
||
Reporter | ||
Comment 13•18 years ago
|
||
A possible heuristic: the event won't be dispatch if the TARGET (and target only) is a disabled form control, AND the event ISN'T a Mutation event.
Other use cases should be determined.
About tc 10 - the disabled button wants to capture the image's load event. It should be allowed.
Reporter | ||
Comment 14•18 years ago
|
||
My previous heuristic sucks :p
Just prevent any event caused by user input, like mouse events and key events.
Comment 15•18 years ago
|
||
Not a blocker, but we'd take a fix if we get one in time.
Flags: blocking1.9? → blocking1.9-
Whiteboard: [wanted-1.9]
Updated•17 years ago
|
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Updated•16 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Comment 16•11 years ago
|
||
Given that we are deprecating mutation events, let's just WONTFIX this.
MutationObservers are the future.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 18•11 years ago
|
||
MutationObservers are cool, but that's not the reason a disabled element should have ALL events broken. What about animationstart etc. ?
btw.
https://bugzilla.mozilla.org/show_bug.cgi?id=952986
You need to log in
before you can comment on or make changes to this bug.
Description
•