Sent by Alex Jones on 23 July 2003 17:05
At 10:20 AM 7/23/2003, Nelson_Rodriguez-Pena wrote:
> >> - Classes, IDs and elements are listed in alphabetical order unless
> >> otherwise noted...
>
>This is not completely right, since the order has a value when evaluating
>rules, so most times you may want to establish a precise order, for
>instance: I want to specify in BODY general attributes, but use specific
>ones in ACRONYM. It can be done if I use:
>
>body{...}
>acronym{..}
>
>but not
>
>acronym{..}
>body{...}
>
>With IDs the same thing happen, position inside the document is relevant.
>
>I think this apply to all your other structure as well...
Really? I thought the cascade applied to the order in which the styling is
applied as opposed to the order it is in within the style sheet (unless
there are conflicting style sheets or in-line styles defining the same
element, class or ID). My understanding of the cascading order (
http://www.w3c.org/TR/CSS1#the-cascade -Rule 4) leads me to believe that
the acronym element is more specific than the body and thus its style rules
would take precedence over those set in the body. My experience has shown
this to be the case for all but :link and its cohorts.
Alex
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
