Side navigation
#995 closed enhancement (wontfix)
Opened February 23, 2007 05:08PM UTC
Closed July 15, 2007 03:07PM UTC
Support XPath position selector: [n]
| Reported by: | joern | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.1.4 |
| Component: | core | Version: | 1.1.3 |
| Keywords: | selectors, xpath | Cc: | |
| Blocked by: | Blocking: |
Description
Being able to replace the rather noisy ":eq(n)" with a plain "[n]" would be great. That is, the following are equivalent:
input:eq(3) <==> input![3]
Thats a great XPath feature!
Attachments (0)
Change History (6)
Changed February 23, 2007 05:08PM UTC by comment:1
| description: | Being able to replace the rather noisy ":eq(n)" with a plain "[n]" would be great. That is, the following are equivalent:\ \ input:eq(3) <==> input[3]\ \ Thats a great XPath feature! → Being able to replace the rather noisy ":eq(n)" with a plain "[n]" would be great. That is, the following are equivalent:\ \ input:eq(3) <==> input![3]\ \ Thats a great XPath feature! |
|---|
Changed March 24, 2007 05:39PM UTC by comment:2
| need: | → Test Case |
|---|
Changed March 25, 2007 03:32AM UTC by comment:3
| resolution: | → fixed |
|---|---|
| status: | new → closed |
Added in SVN rev [1579].
Changed April 06, 2007 01:48PM UTC by comment:4
| resolution: | fixed |
|---|---|
| status: | closed → reopened |
It seems like [n] actually works like nth-of-type(), not like nth-child().
Still, it isn't the same as :eq(n), which is fine.
Changed April 28, 2007 03:46PM UTC by comment:5
Removed in SVN rev [1811].
Changed July 15, 2007 03:07PM UTC by comment:6
| description: | Being able to replace the rather noisy ":eq(n)" with a plain "[n]" would be great. That is, the following are equivalent:\ \ input:eq(3) <==> input![3]\ \ Thats a great XPath feature! → Being able to replace the rather noisy ":eq(n)" with a plain "[n]" would be great. That is, the following are equivalent: \ \ input:eq(3) <==> input![3] \ \ Thats a great XPath feature! |
|---|---|
| milestone: | 1.1.3 → 1.1.4 |
| resolution: | → wontfix |
| status: | reopened → closed |
| version: | 1.1.1 → 1.1.3 |
Unfortunately, since this was backed out - and since we're removing XPath functionality in jQuery 1.2, it really doesn't look like this will make it in.