Closed
Bug 74220
Opened 24 years ago
Closed 19 years ago
NodeRemovedFromDocument Mutation Event Needs Implemented
Categories
(Core :: DOM: Events, enhancement, P3)
Core
DOM: Events
Tracking
()
mozilla1.0.1
People
(Reporter: pbwiz, Assigned: WeirdAl)
References
Details
(Keywords: testcase)
Attachments
(1 file)
1.63 KB,
text/html
|
Details |
NodeRemovedFromDocument Mutation event needs implemented.
Jeff.
Comment 1•24 years ago
|
||
Marking NEW.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: other → All
Hardware: PC → All
Summary: NodeRemovedFromDocument Mutation Event Needs Implemented → [RFE] NodeRemovedFromDocument Mutation Event Needs Implemented
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla1.0.1
Updated•23 years ago
|
Priority: -- → P3
Summary: [RFE] NodeRemovedFromDocument Mutation Event Needs Implemented → NodeRemovedFromDocument Mutation Event Needs Implemented
Comment 2•22 years ago
|
||
I don't understand the difference between DOMNodeRemovedFromDocument and
DOMNodeRemoved. Can someone explain?
DOMNodeRemoved
Fired when a node is being removed from its parent node. This event is
dispatched before the node is removed from the tree. The target of this event is
the node being removed.
* Bubbles: Yes
* Cancelable: No
* Context Info: relatedNode holds the parent node
DOMNodeRemovedFromDocument
Fired when a node is being removed from a document, either through direct
removal of the Node or removal of a subtree in which it is contained. This event
is dispatched before the removal takes place. The target of this event is the
Node being removed. If the Node is being directly removed the DOMNodeRemoved
event will fire before the DOMNodeRemovedFromDocument event.
* Bubbles: No
* Cancelable: No
* Context Info: None
Comment 3•21 years ago
|
||
Depends on: 231676
Assignee | ||
Comment 4•19 years ago
|
||
I think I might implement this (I'm hacking nsDocument for mutation events
anyway for for bug 201236), but I will not attempt to follow bug 231676.
Assignee: hyatt → ajvincent
Status: ASSIGNED → NEW
Assignee | ||
Comment 5•19 years ago
|
||
The testcase given is not comprehensive enough. DOMNodeRemovedFromDocument
fires once for every node removed, directly or indirectly. If you remove the
bar element from:
<foo><bar><one/><two/></bar></foo>
Then you must fire:
(no specific order to the first three)
DOMNodeRemovedFromDocument @ one
DOMNodeRemovedFromDocument @ two
DOMNodeRemovedFromDocument @ bar
NodeRemoved @ bar
and then remove the bar element.
Assignee | ||
Comment 6•19 years ago
|
||
Marking as dup of bug 74219, which will require nearly identical work to implement.
*** This bug has been marked as a duplicate of 74219 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•