Bug Tracker

Opened 12 years ago

Closed 12 years ago

#8383 closed bug (invalid)

.closest() doesn't work with > selector

Reported by: [email protected] Owned by:
Priority: undecided Milestone: 1.next
Component: unfiled Version: 1.5
Keywords: Cc:
Blocked by: Blocking:


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

Change History (3)

comment:1 Changed 12 years ago by anonymous

Or thinking about it more, the use case I have woudl involve treating the context as the top-level parent, so that


returns the child of context that matches sel2 and contains sel1

comment:2 Changed 12 years ago by [email protected]

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

comment:3 Changed 12 years ago by dmethvin

Resolution: invalid
Status: newclosed

Closed per your request.

Note: See TracTickets for help on using tickets.