From: "bill scheider" <[EMAIL PROTECTED]>
>are there strategies
>that can be helpful for the box model in earlier versions of IE?
Ian has given you some suggestions that will work. Probably the simplest way to
deal with the IE5s however is just to write two of the same property rules with
different values, the first for IE5.x/Win and the second for all other
browsers. The second rule should have an escape placed within the property
name, before a letter that is not one of the first six of the alphabet (a-f).
The escape will prevent the IE5.x browsers from reading the redefinition of the
property. This can be done right in a main style sheet with no hiding other
than the escape. An example follows -
#wrapper {
width: 778px;
w\idth: 760px;
padding: 0 8px;
border: 1px solid #036;
}
The "wrapper" will be 778px in all browsers. The IE5s will still place the
border and padding inside the stated width, but the "inside" will be bigger to
start with, the same width as other browsers (and IE6 in standards mode) that
place the padding and border on the outside of the stated content width.
"Double definitions" for box issues are the only way to resolve descrepencies
between the IE5.x/Win broken box model, and the W3C box model if you are using
width-defined boxes with padding and/or borders. Where you put your "hacked"
definitions is up to you, whether in the regular style sheet as shown, filtered
as Ian suggested, or in a separate style sheet called from a Conditional
Comment.
Note: If you have height-defined elements with border and/or padding, the same
problem occurs with the IE5.x/Win browsers. The solution method is the same.
~holly
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
