Modify ↓
Ticket #3850 (closed bug: wontfix)
.find('>') fails in jq 1.3
| Reported by: | StaticShock | Owned by: | john |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.1 |
| Component: | selector | Version: | 1.3 |
| Keywords: | children selector | Cc: | |
| Blocking: | Blocked by: |
Description
this used to be a valid selector in 1.2.6, equivalent to .children()
here's a test case:
javascript:alert($('div').find('>').length);void(0)
Milestone: 1.3.1 Version: 1.3
Change History
comment:1 Changed 4 years ago by john
- Status changed from new to closed
- Version set to 1.3
- Resolution set to wontfix
- Milestone set to 1.3.1
comment:2 Changed 4 years ago by StaticShock
yes, but a query such as:
.find('>:last div').end()
now turns into:
.children(':last').find('div').end().end()
which is hardly as pleasant as it used to be in 1.2.6
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Note: See
TracTickets for help on using
tickets.

I don't think we can guarantee that being a valid selector, thankfully we have a drop-in replacement. Instead of .find('>') just do: