Bug Tracker

Changes between Initial Version and Version 1 of Ticket #7612, comment 1


Ignore:
Timestamp:
Nov 24, 2010, 5:11:25 AM (12 years ago)
Author:
jitter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7612, comment 1

    initial v1  
    55> Get the first ancestor element that matches the selector, '''beginning at the current element''' and progressing up through the DOM tree.
    66
    7 So this is the expected behavior maybe you intended to use `parents()` which doesn't consider the current element as potential match.
     7So this is the expected behavior maybe you intended to use `parents()` which doesn't consider the current element as potential match. The documentation on `closest()` includes a list of the differences between these similar methods and even a sample for the exact behavior you experienced