Skip to main content

Bug Tracker

Side navigation

#7528 closed bug (wontfix)

Opened November 16, 2010 01:58AM UTC

Closed June 06, 2011 06:45PM UTC

$("> a, > p") may not work correctly

Reported by: john Owned by: john
Priority: low Milestone: 1.next
Component: selector Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:
Description

Need to follow-up on this comment.

Attachments (0)
Change History (16)

Changed November 16, 2010 01:59AM UTC by john comment:1

component: unfiledselector
owner: → john
status: newassigned

Specifically the second selector won't work correctly - we need to parse that properly, presumably. A QUnit test case would be good here (applied against Sizzle).

Changed November 16, 2010 05:28AM UTC by john comment:2

keywords: → needstest
milestone: 1.51.4.5
priority: undecidedlow

Changed December 04, 2010 02:15AM UTC by jitter comment:3

live test case shows that this is indeed failing.

Changed April 17, 2011 06:34AM UTC by john comment:4

priority: lowblocker

Changed April 17, 2011 07:30AM UTC by timmywil comment:5

keywords: needstest

Changed April 17, 2011 07:32AM UTC by timmywil comment:6

#6279 is a duplicate of this ticket.

Changed May 22, 2011 04:35PM UTC by john comment:7

description: Need to follow-up on this comment: \ https://github.com/jeresig/sizzle/commit/f6051c1d33aa3f819dfe5fb2fbdc09d51daff16d#commitcomment-169437Need to follow-up on [https://github.com/jeresig/sizzle/commit/f6051c1d33aa3f819dfe5fb2fbdc09d51daff16d#commitcomment-169437 this comment].

Changed May 22, 2011 07:27PM UTC by john comment:8

keywords: → 1.7-discuss

Nominating ticket for 1.7 discussion.

Changed May 22, 2011 09:35PM UTC by rwaldron comment:9

+0,

Changed May 23, 2011 12:24AM UTC by jaubourg comment:10

+0,

Changed May 23, 2011 04:03AM UTC by timmywil comment:11

description: Need to follow-up on [https://github.com/jeresig/sizzle/commit/f6051c1d33aa3f819dfe5fb2fbdc09d51daff16d#commitcomment-169437 this comment].Need to follow-up on [https://github.com/jquery/sizzle/commit/f6051c1d33aa3f819dfe5fb2fbdc09d51daff16d#commitcomment-169437 this comment].

Changed June 03, 2011 01:45PM UTC by john comment:12

-1, Considering that we're likely deprecating leading > selectors anyway, this seems like a very low priority issue.

Changed June 03, 2011 03:42PM UTC by scottgonzalez comment:13

+1, PLEASE PLEASE PLEASE don't deprecate selectors starting with >. This is extremely useful for building generic plugins that allow customizing which elements to work against.

Changed June 05, 2011 09:06PM UTC by ajpiano comment:14

+0, I guess this depends on the outcome of the decision on leading > selectors...

Changed June 06, 2011 03:59PM UTC by jzaefferer comment:15

+0

Changed June 06, 2011 06:45PM UTC by rwaldron comment:16

keywords: 1.7-discuss
priority: blockerlow
resolution: → wontfix
status: assignedclosed