Ian Rastall wrote:[color=blue]
>
> The site is a header (which is a table) and a main <div> underneath
> that. The main <div> is set to have a top margin of 3%, which works
> fine, except in NN4. There, it looks like it has a margin of 20%, or
> even larger.
>
> I couldn't fix it with the @import hack, so I thought I might try
> JavaScript. I tried something like this:
>
> <script language="JavaScript" type="text/javascript">
> if (document.layers) frank.styles.margin-top = "-20%"[/color]
AFAIK you can only access a DIV element through javascript in NS4 if it
is positioned. If it *is* positioned, then
if(document.layers)
document.layers['frank'].style.marginTop=....;
might get you access to the style object property of the layer and set
its top margin. At the same time, a positioned element might better
placed using top and left properties than margin. [Note javascript style
properties use interCaps spelling to replace CSS hyphenated names.]
<snip>
Would NN4 even understand[color=blue]
> something like this?
>[/color]
Probably not. NS4 used CSS positioning before it became standardised,
and has multiple errors and inconsistencies with standard CSS.
To understand what NS4 *might* be doing with your percentage values,
take a Header element like
<h1 style="font-size:200%">Hello</h1>
The percentage size is calculated on the default font-size of H1 and not
the containing body (resulting in a font size of 400% for the H1
element.) This taking base percentage from the wrong place and generally
getting inheritance wrong or losing track of it is a big feature of NS4.
Even with care, absolute measurements (px or pt) may be required for NS4.
The other alternative is to put *all* CSS in the stylesheet, and use
@media rules to make sure *none* of it is visible to NS4, which can then
render using its default style sheet and present like a version 3 browser.
Dom
