Michael Fesser wrote:[color=blue]
> .oO(Jeff Thies)
>
>[color=green]
>>We can do this:
>>
>><tr class="data odd">
>>
>>Can we make a rule that applies when only both classes are present?
>>
>>
>>I suppose I could do this:
>>
>><table class="data">
>><tr class="odd">...
>><tr class="even">...[/color]
>
>
> Why do you need a class on every row?[/color]
I haven't written any of this yet. I don't see a problem with labeling
both odd and even rows and using whichever you want later. Worse code
bloat happens!
And what's wrong with the class[color=blue]
> "data" on the table-element? Do you really want to have _two_ classes
> applied to _every_ row? I would try to keep the number of classes as
> small as possible, which means to make more use of cascading rules and
> descendant selectors.[/color]
I'll probably do that, set either the odd or even rows as a descendant
of the table class. I agree with minimizing number of classes to
increase readability.
This will all be server generated and styled from a gloabl stylesheet.
Some data looks good grey barred and some doesn't.
I probably won't use the double class here, but I have found it usefull
when you want to take the same generated html and use it for different
purposes.
Cheers,
Jeff
[color=blue]
>
> Micha[/color]
two class specific 
