Bug Tracker

Changes between Initial Version and Version 6 of Ticket #10290


Ignore:
Timestamp:
Sep 16, 2011, 9:57:25 AM (10 years ago)
Author:
Rick Waldron
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10290

    • Property Status changed from new to reopened
    • Property Component changed from unfiled to traversing
    • Property Priority changed from undecided to low
    • Property Milestone changed from None to 1.8
    • Property Keywords 1.8-discuss added
  • Ticket #10290 – Description

    initial v6  
    1 http://ejohn.org/blog/element-traversal-api/ [[BR]]
     1 [[BR]]
    22Three years past, now all major browser are supporting element traversing api. Maybe it's time to reconsider?
    33
    44In some cases, this properties can noticeable increase iterating speed --
    55[[BR]]
    6 nextAll( http://jsperf.com/element-traversing-nextall-with-obstacles ),
     6nextAll( ),
    77[[BR]]
    8 children( http://jsperf.com/element-traversing-children-with-obstacles ),
     8children( ),
    99[[BR]]
    10 siblings( http://jsperf.com/element-traversing-siblings-with-obstacles ).
     10siblings( ).
    1111
    1212In some cases, speed increase is less noticeable --
    1313[[BR]]
    14 nextAll( http://jsperf.com/element-traversing-nextall ),
     14nextAll( ),
    1515[[BR]]
    16 children( http://jsperf.com/element-traversing-children ),
     16children( ),
    1717[[BR]]
    18 siblings( http://jsperf.com/element-traversing-siblings ).
     18siblings( ).
    1919
    2020Or practically does not exits --
    2121[[BR]]
    22 parents( http://jsperf.com/element-traversing-parents-with-obstacles ).
     22parents( ).