Sent by Alicia Lane on 23 July 2003 16:04
on 7/23/03 10:20 AM, Nelson Rodriguez-Pena at [EMAIL-REMOVED] wrote:
> ... 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 agree - I list all general attributes first and then tackle the document
structure and specific attributes, in order of location.
This method also makes it easier to troubleshoot bugs. With the style rules
ordered by location, you can examine a troublesome spot AND the rules being
applied to elements surrounding it. An alphabetical listing of style rules
would make this very difficult.
Besides, applications usually have shortcut keys for the "Find" function if
you're looking for a specific rule, so that seems to eliminate the need for
alphabetical indexing.
Great idea to put together a methodology. I'd love to see the finished list.
Regards,
Alicia
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
