nsIDOMTreeWalker.nextNode() causes some attributes to change

RESOLVED INVALID

Status

()

RESOLVED INVALID
13 years ago
6 years ago

People

(Reporter: WeirdAl, Unassigned)

Tracking

({dom2, testcase})

Trunk
x86
Windows XP
dom2, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

1.58 KB, application/vnd.mozilla.xul+xml
Details
(Reporter)

Description

13 years ago
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.
(Reporter)

Comment 1

13 years ago
Created attachment 216279 [details]
testcase
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).
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
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.
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().
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.
Component: DOM: Traversal-Range → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.