Skip to main content

Bug Tracker

Side navigation

#2683 closed bug (duplicate)

Opened April 12, 2008 08:51PM UTC

Closed March 31, 2011 03:23AM UTC

Last modified September 27, 2011 03:55AM UTC

: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

Attachments (0)
Change History (6)

Changed April 13, 2008 11:44AM UTC by upandhigh comment:1

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.

Changed November 13, 2010 07:06PM UTC by dmethvin comment:2

component: coreselector
milestone: 1.2.4
priority: majorlow
status: newopen
version: 1.2.31.4.3

http://jsfiddle.net/dmethvin/6vg6E/

:has(:contains()) works fine but :has(:not(:contains())) dies.

Changed March 30, 2011 09:04PM UTC by danheberden comment:3

milestone: → 1.7

Changed March 31, 2011 03:23AM UTC by danheberden comment:4

resolution: → duplicate
status: openclosed

Changed March 31, 2011 03:23AM UTC by danheberden comment:5

Duplicate of #8720.

Changed September 27, 2011 03:55AM UTC by dmethvin comment:6

milestone: 1.7