Skip to main content

Bug Tracker

Side navigation

#7964 closed enhancement (fixed)

Opened January 13, 2011 09:03PM UTC

Closed January 14, 2011 04:23PM UTC

Some traversal methods perform an unnecessary uniqueness check

Reported by: scottgonzalez Owned by: scott_gonzalez
Priority: low Milestone: 1.5
Component: traversing Version: 1.4.4
Keywords: Cc: jeresig
Blocked by: Blocking:

Methods like .children(), .next() and .prev() are guaranteed to produce a unique result when called on a unique set. These methods are generated by a function which always checks for uniqueness if the original set contained more than one element. Methods that are guaranteed to produce a unique result should not go through the uniqueness check as this is fairly expensive in some browsers.

Attachments (0)
Change History (2)

Changed January 13, 2011 09:10PM UTC by addyosmani comment:1

cc: → jeresig
owner: → scott_gonzalez
priority: undecidedlow
status: newassigned

Changed January 14, 2011 04:23PM UTC by john comment:2

component: unfiledtraversing
milestone: 1.next1.5
resolution: → fixed
status: assignedclosed

This pull request was landed: