#2683 closed bug (duplicate)
:has and :not pseudo-selectors don't play well together
Reported by: | nkallen | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | selector | Version: | 1.4.3 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
$('tr:has(td.name:contains(bob))') this works
$('tr:has(td.name:not(:contains(bob)))') this doesn't
$('td.name:not(:contains(bob))') this does
See http://pastie.caboo.se/177061 for full details
Change History (6)
comment:1 Changed 15 years ago by
comment:2 Changed 12 years ago by
Component: | core → selector |
---|---|
Milestone: | 1.2.4 |
Priority: | major → low |
Status: | new → open |
Version: | 1.2.3 → 1.4.3 |
http://jsfiddle.net/dmethvin/6vg6E/
:has(:contains()) works fine but :has(:not(:contains())) dies.
comment:3 Changed 12 years ago by
Milestone: | → 1.7 |
---|
Better running usecase: http://jsfiddle.net/danheberden/6vg6E/2/
comment:4 Changed 12 years ago by
Resolution: | → duplicate |
---|---|
Status: | open → closed |
comment:6 Changed 12 years ago by
Milestone: | 1.7 |
---|
Note: See
TracTickets for help on using
tickets.
as I know atm jQuery supports only one level nesting. so it's because your second variant doesn't work.
tr:has(td.name:not(someval)) - it's one level nesting and this one is OK tr:has(td.name:not(:contains(someval))) - this one is second level nesting and atm jQuery doesn't support it.