> /*div#content:first-child > * { margin-top: 0; } delete
> ruleset*/
> /*div#sidebar:first-child > * { margin-top: 0;
> }delete ruleset*/
> p {border: 1px solid red;margin: 0 0 15px
> 0;}/*add ruleset*/
David,
That works in the one example, but the purpose of me setting these the way I
did was so that ANY element that was the FIRST element in either of those
DIVs would have a margin-top value of 0 pixels. It's a heck of a lot less
coding that doing a universal reset on all possible elements, and then
having to make all vertical margin adjustments using only the bottom one.
Also, this will be destined for a user-maintainable CMS setup. So while I
could always create a "first-element" class that has a margin-top value of
0, I have no guarantee that the end-user content editor will remember to
apply that class the first element --OR-- remove it if a previous
first-element now falls lower into the content.
...Rob
____________________________________
Rob Emenecker @ Hairy Dog Digital
www.hairydogdigital.com
Please note: Return e-mail messages are only accepted from discussion groups
that this e-mail address subscribes to. All other messages are automatically
deleted.
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
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/
