Opened 13 years ago
Closed 12 years ago
#7528 closed bug (wontfix)
$("> 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 (last modified by )
Need to follow-up on this comment.
Change History (16)
comment:1 Changed 13 years ago by
| Component: | unfiled → selector |
|---|---|
| Owner: | set to john |
| Status: | new → assigned |
comment:2 Changed 13 years ago by
| Keywords: | needstest added |
|---|---|
| Milestone: | 1.5 → 1.4.5 |
| Priority: | undecided → low |
comment:4 Changed 12 years ago by
| Priority: | low → blocker |
|---|
comment:5 Changed 12 years ago by
| Keywords: | needstest removed |
|---|
comment:7 Changed 12 years ago by
| Description: | modified (diff) |
|---|
comment:11 Changed 12 years ago by
| Description: | modified (diff) |
|---|
comment:12 Changed 12 years ago by
-1, Considering that we're likely deprecating leading > selectors anyway, this seems like a very low priority issue.
comment:13 Changed 12 years ago by
+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.
comment:14 Changed 12 years ago by
+0, I guess this depends on the outcome of the decision on leading > selectors...
comment:16 Changed 12 years ago by
| Keywords: | 1.7-discuss removed |
|---|---|
| Priority: | blocker → low |
| Resolution: | → wontfix |
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
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).