W3C home > Mailing lists > Public > www-style@w3.org > October 1997

Re: CSS1 and tables

From: Derek Harding <derek@tpd.com>
Date: Mon, 6 Oct 1997 21:07:43 -0700
To: "Chris Wilson (PSD)" <cwilso@MICROSOFT.com>, <www-style@w3.org>
Message-ID: <01bcd2d6$8f8d7ce0$b79488ce@flasheart.tpdinc.com>
This is most odd since even now Netscape & IE display the following
differently. I don't follow why broken legacy is supported if its not for
uniformity across browsers.

<font face="arial">
<p>This is arial in IE & Netscape.
<table><tr><td>This is arial in IE, it will be the default font in
NS</td></tr></table>
This is arial in both.</p>
</font>

Derek
---
Derek Harding
Technical Director, TPD Publishing
http://www.tpd.com/~derek/
__________________________________________________________________________
Never trust any complicated cocktail that remainds perfectly clear until
the last ingredient goes in, and then immediately clouds.
        -- Terry Pratchett, alt.fan.pratchett

-----Original Message-----
From: Chris Wilson (PSD) <cwilso@MICROSOFT.com>
To: 'Chris Lilley' <Chris.Lilley@sophia.inria.fr>; 'David Perrell'
<davidp@earthlink.net>; www-style@w3.org <www-style@w3.org>
Date: Monday, October 06, 1997 6:39 PM
Subject: RE: CSS1 and tables


>Ah, an interesting solution - one I discarded while planning in IE3
>because of the legacy of:
>
> <FORM STYLE="font-weight: bold">This is bold.
> <INPUT ID=a>
> <TABLE><TR><TD>
> <INPUT ID=b>This is not bold.
> </TD></TR>
> </TABLE>
> This is bold again.
> <INPUT ID=c>
> </FORM>
>
>Namely, you can't assume you can always break an element into two or
>more elements without damaging its functionality.
> -Chris
>Chris Wilson
>cwilso@microsoft.com
>***
>
>> -----Original Message-----
>> From: Chris Lilley [SMTP:Chris.Lilley@sophia.inria.fr]
>> Sent: Monday, October 06, 1997 3:39 PM
>> To: Chris Wilson (PSD); 'David Perrell'; www-style@w3.org
>> Subject: Re: CSS1 and tables
>>
>> On Oct 6,  2:59pm, Chris Wilson (PSD) wrote:
>>
>> > Unfortunately (and believe me, I do mean "unfortunately"), legacy
>> > rendering disagrees with you quite strongly.  Try loading this in
>> any
>> > version of Netscape Navigator or Internet Explorer:
>> >
>> > <B>This is bold.
>> > <TABLE><TR><TD>
>> > This is not bold.
>> > </TD></TR>
>> > </TABLE>
>> > This is bold again.
>> > </B>
>>
>> OK, so these browsers do error correction on a document which has
>> a block  level element inside a phrase level element, and internally
>> generate
>>
>> <B>This is bold.</b>
>> <TABLE><TR><TD>
>> This is not bold.
>> </TD></TR>
>> </TABLE>
>> <b>This is bold again.</B>
>>
>> Fine. But, since TABLE is not a child of B, naturally the table is
>> not in bold.
>>
>>
>> --
>> Chris Lilley, W3C                          [ http://www.w3.org/ ]
>> Graphics and Fonts Guy            The World Wide Web Consortium
>> http://www.w3.org/people/chris/              INRIA,  Projet W3C
>> chris@w3.org                       2004 Rt des Lucioles / BP 93
>> +33 (0)4 93 65 79 87       06902 Sophia Antipolis Cedex, France
>
>
Received on Tuesday, 7 October 1997 00:08:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:51 GMT