331735 - nsIDOMTreeWalker.nextNode() causes some attributes to change

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Alex Vincent [:WeirdAl]]

I've a testcase which shows the tree walker's nextNode() method (probably indirectly, through XBL) causing attributes to be set, and firing DOM mutation events.

Testcase coming up.

Comment 1

[Alex Vincent [:WeirdAl]]

Attachment: testcase

Comment 2

[Boris Zbarsky [:bzbarsky]]

Nothing wrong with this behavior, per se (other than that the mutation events bubble out of anonymous content, which is covered by other bugs as I recall).

Comment 3

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

Btw, we should now be able to rewrite the treewalker to use nsINode rather then nsIDOMNode. Not sure if that'll get rid of the events since I don't know where they're coming from.

Comment 4

[Boris Zbarsky [:bzbarsky]]

I bet it won't, since looking at the code and the stack in Alex's blog I bet we're attaching the XBL when we wrap the DOMNode in a JSObject for return from nextNode().

Comment 5

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

Ah, makse sense, so no, won't help then. Though, this bug is probably rather a dup of the 'don't bubble mutations out of bindings' bug then invalid.