Closed
Bug 331735
Opened 19 years ago
Closed 19 years ago
nsIDOMTreeWalker.nextNode() causes some attributes to change
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: WeirdAl, Unassigned)
Details
(Keywords: dom2, testcase)
Attachments
(1 file)
1.58 KB,
application/vnd.mozilla.xul+xml
|
Details |
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•19 years ago
|
||
![]() |
||
Comment 2•19 years ago
|
||
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
Closed: 19 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.
![]() |
||
Comment 4•19 years ago
|
||
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.
Updated•12 years ago
|
Component: DOM: Traversal-Range → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•