|
|
Posted by Bone Ur on 11/21/07 19:52
Well bust mah britches and call me cheeky, on Wed, 21 Nov 2007 18:24:38
GMT Shelly 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.
That's the right way to comment-out a line in the <style> element.
> As far as handling it correctly, what was wrong with the line:
>
> padding: 3px 0 0 0;
>
> that caused it to flicker?
I can only guess, but first of all, ie handles margins and padding
differently than standards-compliant browsers. Whether that is relevant
may not be pertinent in any case; it just might be simply a matter of ie
redrawing the page with margins/padding included on hover styles and
execution.
Maybe someone here knows more about it. I just chalk it up to the
"brokenness" of ie.
--
Bone Ur
Cavemen have formidable pheromones.
Navigation:
[Reply to this message]
|