![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| ||||||
| ||||||
|
|
You do not show a tr part that is not covered by a td. |
|
That some or all present browsers and perhaps the W3 specs have implemented this illogicality of CSS syntax, dos not mean we should follow it. |
|
The same as for <tr> goes for <thead> and <tbody>, should they have background colour that is not visible by itself but only for the pedegree TDs? |
|
See here that the backgrounds of the tr and tbody in both middle rows are NOT coloured: |
|
I would prefer to use the complete syntax, because that is what is implremented in fact: table tbody tr td {background-color: blue;} table.a tbody tr:hover td { background-color: #c9c9c9; } table.b tbody:hover tr td { background-color: #c9c9c9; } |
|
The idea that elements can cascade properties that they themselfs do not show is correct, but only if they get that property from higher up the cascade chain. To assign such property to that element itself, while at present possible, seems ridiculous to me. |
ink;
#2
| |||||
| |||||
|
|
Evertjan. kirjoitti: You do not show a tr part that is not covered by a td. To quote TL: non sequitur. That some or all present browsers and perhaps the W3 specs have implemented this illogicality of CSS syntax, dos not mean we should follow it. Hmm.. what's that illogicality and who's that we? |
|
The same as for <tr> goes for <thead> and <tbody>, should they have background colour that is not visible by itself but only for the pedegree TDs? I must be more tired than I thought, 'cause I can't understand the question. |
|
See here that the backgrounds of the tr and tbody in both middle rows are NOT coloured: Ok, my fault for playing the empirical game. IOW, this proves nothing. |
|
I would prefer to use the complete syntax, because that is what is implremented in fact: table tbody tr td {background-color: blue;} table.a tbody tr:hover td { background-color: #c9c9c9; } table.b tbody:hover tr td { background-color: #c9c9c9; } IIRC, superfluous references to elements when classes would suffice are a hindrance? |
|
The idea that elements can cascade properties that they themselfs do not show is correct, but only if they get that property from higher up the cascade chain. To assign such property to that element itself, while at present possible, seems ridiculous to me. I'm not sure of your meaning, something like the following? style type="text/css" tr { display:block; background-color:red; height:100px; } td { display:inline; background-color ink;height:50px; } /style Anyways, this has nothing to do with JS. Follow up to CIWAS. |
![]() |
| Thread Tools | |
| Display Modes | |
| |