> From: <[EMAIL PROTECTED]>
>
>>
>> Ya gotta try this just for fun even if you don't answer my question. Go
>> here in BOTH your IE browser AND your FF browser:
>> http://lafontainerealestate.com/lafontainerealestate.com/1280/s/c/x/en-us/test
>> (This is set for a screen resolution of 1280, fo
ot;, "topmargin", "marginwidth", and "valign"). Outside of that,
verything else checked out through both validators. Yet, the problems persist!
TIA,
Tony
Original Message-
rom: Mike A <[EMAIL PROTECTED]>
o: css-d@lists.css-discuss.org
ent: Fri, 12 Oct 2007
arginwidth", and "valign"). Outside of that,
everything else checked out through both validators. Yet, the problems persist!
TIA,
Tony
-Original Message-
From: Mike A <[EMAIL PROTECTED]>
To: css-d@lists.css-discuss.org
Sent: Fri, 12 Oct 2007 8:50 am
Subject: Re: [
From: <[EMAIL PROTECTED]>
> At least I don't think it is. As I was studying quirks, it seems that if
> the code breaks after putting an appropriate doctype at the beginning of
> the document, then it is playing according to the quirky rules of earlier
> browsers. But this problem appears in IE6
At least I don't think it is. As I was studying quirks, it seems that if the
code breaks after putting an appropriate doctype at the beginning of the
document, then it is playing according to the quirky rules of earlier browsers.
But this problem appears in IE6 and the latest FF with the appropr
