Steve Pugh wrote:[color=blue]
> DU <drunclear@hotWIPETHISmail.com> wrote:
>[color=green]
>>Frances Del Rio wrote:
>>[color=darkred]
>>>when I test my stuff with the validator in HomeSite it tells me the body
>>>tag no longer reads margin attributes.. does this mean now margins are
>>>to be specified only in CSS?[/color]
>>
>>Yes. marginheight, marginwidth, topmargin, leftmargin, etc... are not
>>supported by MSIE 5+ but are supported by NS 4, NS 6, NS 7. So, if you
>>define these attributes in your document, say, like this:[/color]
>
>
> No. topmargin and leftmargin are supported by IE5+ just as they were
> supported by IE4. (top and left were supported from IE2, but IE4 added
> right and bottom). IE6 and Opera 7 later added support for left and
> top but not right and bottom.
>[/color]
Ok, I was not sure about these. I'll check this for sure.
[color=blue]
> (When only top and left are specified they affect all four margins not
> just the top and left ones, I'm not sure if this is true all the way
> back to IE2 or whether it's a later change.)
>
> marginwidth and marginheight were added as attributes of body (as
> opposed to attributes of frame) by NN4 but are also supported by Opera
> 4+.
>
>[color=green]
>><body marginheight="0" marginwidth="0" topmargin="0" leftmargin="0" ...>
>>then MSIE 5+ will have 15px of margin for top and bottom of the body
>>node and a 10px margin for left and right margin while NS 4, NS 6, NS 7.x,
>>Mozilla-based browsers will have 0 margins.[/color]
>
>
> No. MSIE will also display zero margins with the above code. Try it
> and see for yourself.
>
>[color=green]
>>One simple, obvious and reliable benefit of coding according to W3C web
>>standards is that you avoid all this without even knowing which browsers
>>and which versions of which browsers support what exactly.[/color]
>
>
> However, you do have to remember that in CSS terms IE and Gecko have
> default margins whilst Opera has default padding.
>[/color]
That I know.
Despite errors or imprecisions regarding supported attributes, my
reasoning regarding W3C web standards compliance is still very strong:
if you want future-proof code that can now and will later be supported
and rendered in an overwhelming majority of browsers in use out there,
then going with W3C web standards is the safe, solid, reliable way.
[color=blue]
>[color=green]
>>The stupid thing about margins is that NS 4 does support CSS margins
>>applied to the body;[/color]
>
>
> No it doesn't.[/color]
Well, I tried setting margins many years ago on NS 4.72 on the body node
and it worked.
Try it and see. The only CSS way of placing content[color=blue]
> right up against the window edge in NN4 is absolute positioning.
>
> Steve
>[/color]
That could be another issue...not sure what you mean by placing content.
I was referring to rendering of margin for the body node. This reference
supports my claim:
http://devedge.netscape.com/library/...otes.html#5505
DU
body margins.... 
