This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23268 - Cannot describe NodeIterator in terms of "node is removed"
Summary: Cannot describe NodeIterator in terms of "node is removed"
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 24653
Blocks: 25430
  Show dependency tree / graph
 
Reported: 2013-09-17 20:07 UTC by Anne
Modified: 2014-08-14 14:55 UTC (History)
3 users (show)

See Also:

Attachments

Description Anne 2013-09-17 20:07:57 UTC 
http://dom.spec.whatwg.org/#interface-nodeiterator

[[
Before a node is removed from the iterator collection, these steps must be run: 
]]

Not entirely sure how to hook this into the mutation algorithms.
Comment 1 Anne 2014-02-12 17:03:52 UTC 
Basically, the current setup is wrong.

The node is removed hook needs to be passed removedNode, oldParent, and oldPreviousSibling as arguments. Those can then be used to do various things.
Comment 2 Anne 2014-02-12 18:50:57 UTC 
To be clear, the steps are in fact run after the node is removed. http://mxr.mozilla.org/mozilla-central/source/content/base/src/NodeIterator.cpp#71 has details from Gecko.