|
|
Posted by Shelly on 11/21/07 18:24
Bone Ur wrote:
> Well bust mah britches and call me cheeky, on Wed, 21 Nov 2007
> 03:06:49 GMT Beauregard T. Shagnasty scribed:
>
>>>>> XXpadding: 3px 0 0 0;
>>
>> /* padding: 3px 0 0 0; */
>>
>>> It's just a cheater way of removing the line from counting.
>>> Browsers don't parse malformed css so this is like eliminating it.
>>> I wouldn't advise publishing the page that way; remove the line or
>>> change it so it no longer has the bad effect. -And you're quite
>>> welcome.
>>
>> Using comment markers to 'remove' it is better. <g> Doing so leaves
>> no doubt as to your intentions, and also protects you from next
>> year's browser, which might disregard /all/ CSS from that point on.
>
> Agreed. I use it only for "easier" preliminary testing on browsers
> whose reactions I know from experience. (Saves keystrokes.)
>
> For any permanent change, the line should be dealt with correctly.
What I normally do to eliminate a line but not remove it is to enclose it in
a /* */ set.
As far as handling it correctly, what was wrong with the line:
padding: 3px 0 0 0;
that caused it to flicker?
--
Shelly
Navigation:
[Reply to this message]
|