The jQuery :nth-child selector has an "index" argument which is 1-based. But the jQuery "index" method, which is arguably the converse of the selector, returns a 0-based result. This is very easy to work around once you’re aware of it, but it’s surprising in a library which is, generally, designed both well and consistently.
-
Links
-
Tags
.NET architecture asp.net mvc business C# Change Manager CodeRage columbus columbus architecture group craig gentry Delphi delphi prism Embarcadero encryption entity framework Erlang functional programming generics givecamp homomorphic encryption html humor InterBase javascript jqGrid jQuery jQuery BBQ linq linq to sql math merb Mike Rozlog modeling mvc ndepend Nick Hodges orm rails security software archeology static analysis the dynamic web unit testing uris WebCategories
-
Recent Comments
- wamda on A Math Primer for Gentry’s Fully Homomorphic Encryption
- wamda on A Math Primer for Gentry’s Fully Homomorphic Encryption
- Bryce on Projecting Onto a Presentation Model with the Entity Framework and ASP.NET MVC
- Bryce on Static Analysis and Generated Code
- Roland Bengtsson on Everything You Need to Know About InterBase Character Sets
-
{ 1 } Comments
Yep, banged my head over this too
But I guess they had no choice, as the CSS 3 specification says nth-child indexing is 1-based: http://www.w3.org/TR/2001/CR-css3-selectors-20011113/#nth-child-pseudo
Post a Comment