Jason Pruim wrote:

> One question I did have though... I understand the .content {display:
>  inline;} and the leftColumn {position: relative;} but what does the 
> * html .wrapper {zoom: 1;} do exactly?

It's a 'hasLayout'[1] trigger, and in your case I found the non-valid
'zoom' to work best - alternative (valid) triggers tended to have
negative side-effects. I also had to use the '* html' hack to target IE6
(and below), to avoid conflicts with some of IE7' internal bug-fixes.

Without this 'hasLayout' trigger IE6 seemed to interpret .wrapper's
dimensions a bit unreliable - changed positions for .wrapper's children
when hovering links - which is a clear sign that IE6 couldn't determine
.wrapper's dimensions and relation to other elements.

Triggering 'hasLayout' means to "lay out" the area of .wrapper -
"stiffen up IE6' backbone" so it immediately interprets exactly how wide
.wrapper is, and where to position .wrapper's children relative to
.wrapper's edges. Result: stable rendering.

> I put it up at the top of the css file, and it works, but is that the
>  best place to put it? Or should it go somewhere else?

Put it anywhere you like where IE6 can pick it up, as long as it is
complete - as I wrote it. The CSS validator will flag it as an error
anyway - unless it is hidden in a conditional comment or something to
that effect.

regards
        Georg

[1]http://www.satzansatz.de/cssd/onhavinglayout.html
-- 
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
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/

Reply via email to