Node traversal functions are currently Node and ContainerNode members. Their implementations are scattered over multiple header and source files. These functions have no particular reason to be members as they don't require non-public access. Make them freestanding function instead and gather them together.
Created attachment 178474 [details] patch
Created attachment 178477 [details] patch2
Comment on attachment 178477 [details] patch2 Attachment 178477 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/15219827
Comment on attachment 178477 [details] patch2 Attachment 178477 [details] did not pass cr-android-ews (chromium-android): Output: http://queues.webkit.org/results/15230463
Comment on attachment 178477 [details] patch2 Attachment 178477 [details] did not pass gtk-ews (gtk): Output: http://queues.webkit.org/results/15238361
Comment on attachment 178477 [details] patch2 Attachment 178477 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/15249002
Comment on attachment 178477 [details] patch2 Attachment 178477 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/15242176
Created attachment 178582 [details] patch3
Comment on attachment 178582 [details] patch3 Seems like a great idea. Thank you. :)
Morrita-san, this is relevant to work you're doing on bug 104332.
Created attachment 178586 [details] patch4
Comment on attachment 178586 [details] patch4 Attachment 178586 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/15227785
Created attachment 178654 [details] patch5 Based on Darin's suggestion renamed nextSibling -> nextSkippingChildren
http://trac.webkit.org/changeset/137221
(In reply to comment #10) > Morrita-san, this is relevant to work you're doing on bug 104332. Yeah, I'm thinking about something like NodeRenderingTraversal for encapsulte enabling/disabling ShadowComposedTreeWalker.