288721 - [FIX]DOMNodeInserted MutationEvent does not fire for HTMLButtonElement

Status: RESOLVED FIXED

(Core :: DOM: Events, defect, P2)

Description

[Lucky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

I almost gave up on using this great EventListener because my first test was the
use of createElement('button') .. and append it to a DIVElement.  It would never
fire off the MutationEvent DOMNodeInserted...  Finally, went back and simplified
the code.. and found that pretty much any other elements created in the same way
WOULD fire it successfully?

Reproducible: Always

Steps to Reproduce:
1. document.addEventListener('DOMNodeInserted',yourhandler,true);
2. document.createElement('button');
3. [some element in your document].appendChild(newButton);
4. no DOMNodeInserted event called :(
5. replace the document.createElement() w/ any other element tagName, and success.
Actual Results:  
No DOMNodeInserted event is called from a HTMLButtonElement;
other elements fire that event properly.

Expected Results:  
fire DOMNodeInserted event when button element is appended to DOM

Comment 1

[Lucky]

Attachment: Simple HTML page that shows the dynamic creation of several HTMLElements

This should display the lack of MutationEvent on insertion of
HTMLButtonElement;
Hope it will help you kill this bug quickly.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Attachment: Silly patch

The mutation event dispatch passes a null prescontext, which makes sense... 
Note that if we ever fix dispatchEvent to work without a presentation we'll
need to fix this code to actually deal with a null prescontext, and the same
for input element code, etc...

Comment 3

[Johnny Stenback (:jst)]

Comment on attachment 183244 [details] [diff] [review]
Silly patch

r+sr=jst

Comment 4

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 183244 [details] [diff] [review]
Silly patch

This is no-risk and fixes a silly bug where we don't fire mutation events for
one and only one type of HTML element...

Comment 5

[Boris Zbarsky [:bzbarsky]]

Fixed.