Comments on: jQuery Table Striping Bug

By: Trevor

Trevor — Wed, 18 Jun 2008 17:07:30 +0000

@Andy and Pete-
I see what you are saying. But with that, wouldn’t the nth-child selector work the same way?

By: Pete

Pete — Wed, 18 Jun 2008 16:56:13 +0000

Nice post, but Andy is right. I tried his changes on your tables, and they work like a charm. Sometimes the obvious isn’t so obvious, and I keep stumbling upon dozens of ways to do similar things in jQuery.

Keep up the good work!

By: Andy Couch

Andy Couch — Wed, 18 Jun 2008 14:55:43 +0000

I don’t think this is a jQuery bug. In fact, I would consider this a feature. In your selector, you are telling jQuery to collect all TRs that are inside TABLEs with the “striped” class that appear in the document and then differentiate between the even and odd ones. You aren’t telling jQuery to reset the counter when it encounters a new table. While this might seem like something that should happen automatically, there are many use cases where you wouldn’t want that to happen. I think this is all just part of the power of jQuery. So the easy fix is to just group each table into its own collection, which gives each on its own index. And you could do that with something like this…

$(document).ready(function(){
$(“table.striped”).each(function(){
$(this).find(“tbody tr:odd”).addClass(“odd”);
$(this).find(“tbody tr:even”).addClass(“even”);
});
});

I’m not saying your solution is wrong. This is just another solution that would work too. There are probably a 100 other ways to do it as well.

By: fwolf

fwolf — Wed, 18 Jun 2008 11:36:18 +0000

so basically the counter is not being reset when performing yet another “table striping”-session, aint it?

I havent looked into the source yet, but normally you would create a oddeven-chooser-function like this, ie. using a row counter and then % 2 (true = odd, false = even).

cu, w0lf.