MDN wants to learn about developers like you:


This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.

The NodeIterator.detach() method is a no-op, kept for backward compatibility only.

Originally, it detached the NodeIterator from the set over which it iterates, releasing any resources used by the set and setting the iterator's state to INVALID. Once this method had been called, calls to other methods on NodeIterator would raise the INVALID_STATE_ERR exception. 




var nodeIterator = document.createNodeIterator(
    { acceptNode: function(node) { return NodeFilter.FILTER_ACCEPT; } },
nodeIterator.detach(); // detaches the iterator

nodeIterator.nextNode(); // throws an INVALID_STATE_ERR exception


Specification Status Comment
The definition of 'NodeIterator.detach' in that specification.
Living Standard Transformed in a no-op
Document Object Model (DOM) Level 2 Traversal and Range Specification
The definition of 'NodeIterator.detach' in that specification.
Obsolete Initial definition.

Browser compatibility

Feature Chrome Edge Firefox (Gecko) Internet Explorer Opera Safari
Basic support 1.0 (Yes) 3.5 (1.9.1)
Since 22 (22), acts as a no-op.
9.0 9.0 3.0
Feature Android Edge Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile
Basic support (Yes) (Yes) 1.0 (1.9.1)
Since 22 (22), acts as a no-op.
(Yes) 9.0 3.0

See also

Document Tags and Contributors

 Contributors to this page: abbycar, fscholz, Prome, Khodaidad_Basharmand, teoli, Sheppy, Jürgen Jeka
 Last updated by: abbycar,