Ticket #9725 (closed bug: worksforme)
Undefined response with multiple find()s on the same object
| Reported by: | garytalmes@… | Owned by: | garytalmes@… |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | attributes | Version: | 1.6.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
I'm using jQuery 1.6.1 (minified) on Firefox 4 (Mac, Snow Leopard).
Say I do this:
$("#mydiv").find("ul.firstlist li a.current").attr("myname");
This yields the expected result.
But now on the next line I do this:
$("#mydiv").find("ul.secondlist li a.current").attr("myname");
This yields "undefined" every time, even though the html is correct and the values are there. It seems that performing a second find() on the same object does not work. And it's not just with attribute calls. I tried applying CSS and that did not work. I also tried to see if I was able to reference $("#mydiv") at all, and I could not.
Workaround: prior to the first find() I make a copy of $("#mydiv") and then perform the second find() on the copy.
Change History
comment:1 Changed 23 months ago by ajpiano
- Owner set to garytalmes@…
- Status changed from new to pending
comment:2 Changed 23 months ago by rwaldron
- Priority changed from undecided to low
- Resolution set to worksforme
- Status changed from pending to closed
- Component changed from unfiled to attributes
Works fine: http://jsfiddle.net/rwaldron/bwUFD/
comment:3 Changed 23 months ago by dmethvin
Closer to the description, but yeah it works for me too:
http://jsfiddle.net/dmethvin/bwUFD/1/
garytalmes, this is why a test case is so important. Now two people have taken the time to reproduce the problem and failed.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket! Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, we've created this boilerplate: http://jsfiddle.net/rwaldron/da3nM/ Open the link and click to "Fork" in the top menu.