Gunlaug Sørtun wrote:
> John wrote:
>> Any suggestions on a spot on line with a good explanation of the
>> cascading relationship(s)?
>
> For a complete picture I think "the source" is best...
>
> http://www.w3.org/TR/CSS21/cascade.html#cascade
I'm afraid specifications (or draft specifications) aren't usually very
readable. They are not meant to be tutorials or textbooks but rigorous
descriptions for implementors and other technical people - and for
people who write tutorials etc. The CSS specifications are no exception,
though _some_ parts of them are fairly smooth reading.
The cascade concept is generally misunderstood, but there are many good
textbooks on CSS that explain it pretty well. It's just a difficult
issue and not easily explained in a mailing list discussion.
CSS differs from many other styling approaches in its somewhat
simplistic idea of a style sheet as a collection style rules. Although a
rule may assign values to several properties (for the elements that
match the selector of the rule), this is really just technical grouping.
The rule can conceptually be split to rules that each assign a value to
just one property. Each of these elementary rules is processed
separately in the cascade. I think this is the point that people miss
most often when they think about the cascade.
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
