Hi guys,
I'm stumped. I have inherited this site, and am busy making changes
and adding new sections to it. The stylesheet was a complete mess, and
I've at least managed to tidy it up a little bit, but it's still (I
feel) more complex than it really needed to be. Which of course,
occasionaly cause
On 28/11/05, Chad Lindstrom <[EMAIL PROTECTED]> wrote:
> Add the !important rule.
>
> div.highlightBox p {
> margin-bottom: 0 !important;
> padding-bottom: 0;
> }
>
> That oughta fix it.
You're right, it did. Virtual hugs to Chad! *hugs*
Cheers,
Seona.
___
Seona Bellamy wrote:
> On 28/11/05, Chad Lindstrom <[EMAIL PROTECTED]> wrote:
>
>> Add the !important rule.
...
> You're right, it did. Virtual hugs to Chad! *hugs*
!important usually works, and is fine for debugging _and_ hopeless cases.
Advice: better save !important for cases where nothing
Gunlaug Sørtun wrote:
> !important is our last option (short of using inline-styles with
> !important on top), and overusing it may lead to stylesheets full of
> !important just to make them work. Such stylesheets are not easy to
> maintain at a later date.
Approving Georg's objections, the desper
Hi Ingo,
You wrote:
> Does anyone have examples where !important is a good choice?
I use "!important" in print.styles quite frequently.
e.g. "div { float:none ! important; position:static ! important; }"
is almost mandatory in my print.styles.
Also !important is a good solution to override expr
Rainer Wagener wrote:
> I use "!important" in print.styles quite frequently. e.g. "div {
> float:none ! important; position:static ! important; }" is almost
> mandatory in my print.styles.
I think that's because you organize your styles in such a way that you
have to override a bunch of screen-s
