First, we should move nsContentIterator and nsContentSubtreeIterator into
mozilla namespace and then, remove "ns" prefix.
Additionally, this patch separates the definition of the classes into
ContentIterator.h and exposes it as "mozilla/ContentIterator.h". This allows
everybody access those concrete classes.
Differential Revision: https://phabricator.services.mozilla.com/D15917
--HG--
rename : dom/base/nsContentIterator.cpp => dom/base/ContentIterator.cpp
rename : dom/base/nsContentIterator.cpp => dom/base/ContentIterator.h
extra : moz-landing-system : lando
First, we should move nsContentIterator and nsContentSubtreeIterator into
mozilla namespace and then, remove "ns" prefix.
Additionally, this patch separates the definition of the classes into
ContentIterator.h and exposes it as "mozilla/ContentIterator.h". This allows
everybody access those concrete classes.
Differential Revision: https://phabricator.services.mozilla.com/D15917
--HG--
rename : dom/base/nsContentIterator.cpp => dom/base/ContentIterator.cpp
rename : dom/base/nsContentIterator.cpp => dom/base/ContentIterator.h
extra : moz-landing-system : lando
nsContentIterator in post-order collects nodes starting from deepest first
child to next siblings and parents. I.e., collecting end points (i.e.,
"close tag" if element node). This is tested by
test_content_iterator_post_order.html.
nsContentIterator in pre-order collects nodes starting from most ancestor to
last deepest child node. I.e., collecting start points (i.e., "open tag" if
element node). This is tested by test_content_iterator_pre_order.html.
nsContentSubtreeIterator collects most ancestor nodes which are selected
entirely by specified range or positions. This is tested by
test_content_iterator_subtree.html
I.e., all of them start with "test_content_iterator_" for making find easier.
Differential Revision: https://phabricator.services.mozilla.com/D15286
--HG--
extra : moz-landing-system : lando
Masayuki Nakano
Csoregi Natalia