Bug Tracker

Changes between Initial Version and Version 5 of Ticket #9747


Ignore:
Timestamp:
Jul 6, 2011, 9:40:49 AM (9 years ago)
Author:
Rick Waldron
Comment:

Just because you says it's a bug, does not make it a bug.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9747

    • Property Status changed from new to closed
    • Property Component changed from unfiled to selector
    • Property Priority changed from undecided to low
    • Property Keywords needsdocs added
    • Property Resolution changed from to invalid

  • Ticket #9747 – Description

    initial v5  
    11Affects every version of jQuery that I tested: 1.2.6, 1.3.2, 1.4.4, 1.5.2, 1.6.1.
    22
    3 Reproduced in Chrome 13.0.782.32 beta under Ubuntu 11.04.
     3Reproduced in Chrome beta under Ubuntu 11.04.
    44
    55Steps to reproduce:
    … …  
    1717Every nested element matching the given selectors is returned.  It is as though ":first" has no effect on result of the find() invocation.
    1818
    19 jsfiddle test case: http://jsfiddle.net/hallettj/q9zfd/1/
     19jsfiddle test case:
    2020
    2121If I combine both selectors into one jQuery() call instead of using a chained find() invocation then the result is as I expect.  For example, `$('li a:first')` returns a single anchor tag: the one in the first list item.  But `$('li').find('a:first')` returns every anchor tag in every list item - assuming that each list item has at most one anchor tag.