Skip to content

Implement :nth-child(An+B of selector list) #291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BenjaminPoulain opened this issue Oct 14, 2014 · 5 comments
Closed

Implement :nth-child(An+B of selector list) #291

BenjaminPoulain opened this issue Oct 14, 2014 · 5 comments

Comments

@BenjaminPoulain
Copy link

WebKit has support for CSS4's :nth-child(An+B of selector list). It would be great if sizzle could add the pseudo class to simplify backward compatibility.

The specification is here: http://dev.w3.org/csswg/selectors/#the-nth-child-pseudo
My implementation feedback to W3C: http://lists.w3.org/Archives/Public/www-style/2014Oct/0106.html
The tests of WebKit are here: http://trac.webkit.org/browser/trunk/LayoutTests/fast/selectors/ (all the tests starting with nth-child-of. The most useful outside WebKit are nth-child-of-basics.html and nth-child-of-basics-2.html).

@gibson042
Copy link
Member

This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.

Thanks. Unfortunately, we cannot yet include CSS4 selectors in a release, but will happily consider code if you have a particular implementation in mind. Otherwise, I wouldn't expect anything here until after the spec makes it to Recommendation status.

@gibson042
Copy link
Member

Specifically, though, I've been considering making a CSS4 branch to test the cost of new selectors so they're ready to go on day 1. We'll probably add it when we ship Sizzle 3.0.0 later this year.

@mgol
Copy link
Member

mgol commented Oct 14, 2014

@gibson042 Did you mean Sizzle 3.0? 2.0 is already on npm. ;)

@gibson042
Copy link
Member

Yes, it was a mistranslation of "next major release". Fixed.

@timmywil
Copy link
Member

Duplicate of #237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants