Side navigation
#8383 closed bug (invalid)
Opened February 25, 2011 02:44PM UTC
Closed February 27, 2011 02:04AM UTC
.closest() doesn't work with > selector
| Reported by: | wheresrhys@gmail.com | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.next |
| Component: | unfiled | Version: | 1.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Test case is here: http://jsfiddle.net/77Qm9/
Not sure what correct behaviour should be? Maybe ignore the > completely, i.e treat ">selector" as "selector", rather than returning empty jQuery
Attachments (0)
Change History (3)
Changed February 25, 2011 03:07PM UTC by comment:1
Changed February 25, 2011 05:44PM UTC by comment:2
After reading the specification, I've submitted a new ticket http://bugs.jquery.com/ticket/8384 which is more general... so this one can be closed if you like
Changed February 27, 2011 02:04AM UTC by comment:3
| resolution: | → invalid |
|---|---|
| status: | new → closed |
Closed per your request.
Or thinking about it more, the use case I have woudl involve treating the context as the top-level parent, so that
$(sel1).closest(>sel2,context)
returns the child of context that matches sel2 and contains sel1