366517 - Mutation Events not fired in disabled form controls

Status: RESOLVED WONTFIX

(Core :: DOM: Events, defect)

Description

[Joao Eiras]

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

Comment 1

[Joao Eiras]

Attachment: tc1 - DOMAttrModified in button

Comment 2

[Joao Eiras]

Attachment: tc2 - DOMAttrModified in input

Comment 3

[Joao Eiras]

Attachment: tc3 - DOMAttrModified in select

Comment 4

[Joao Eiras]

Attachment: tc4 - DOMCharacterDataModified in button

Comment 5

[Joao Eiras]

Attachment: tc5 - DOMCharacterDataModified in select

Comment 6

[Joao Eiras]

Attachment: tc6 - DOMNodeInserted in button

Comment 7

[Joao Eiras]

Attachment: tc7 - DOMNodeInserted in select

Comment 8

[Joao Eiras]

Attachment: tc8 - DOMNodeRemoved in button

Comment 9

[Joao Eiras]

Attachment: tc9 - DOMNodeRemoved in select

Comment 10

[Joao Eiras]

Testcase 1 - DOMAttrModified in button works the first time it's loaded. If you refresh it it'll fail.

Comment 11

[Boris Zbarsky [:bzbarsky]]

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.

Comment 12

[Joao Eiras]

Attachment: tc 10 - capturing load listener in disabled button with child image

Comment 13

[Joao Eiras]

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.

Comment 14

[Joao Eiras]

My previous heuristic sucks :p

Just prevent any event caused by user input, like mouse events and key events.

Comment 15

[Johnny Stenback (:jst)]

Not a blocker, but we'd take a fix if we get one in time.

Comment 16

[naugtur]

related: https://bugzilla.mozilla.org/show_bug.cgi?id=952986

Comment 17

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Given that we are deprecating mutation events, let's just WONTFIX this.

MutationObservers are the future.

Comment 18

[naugtur]

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