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

RE: CSS vs. transitional markup [was: No Subject]

From: Chris Wilson (PSD) <cwilso@MICROSOFT.com>
Date: Mon, 4 Aug 1997 09:22:12 -0700
Message-ID: <41F7F4CE3CA2CF11BC5000805F14B2A9023AC005@RED-31-MSG.dns.microsoft.com>
To: "'Douglas Rand'" <drand@sgi.com>, David Perrell <davidp@earthlink.net>
Cc: www-style@w3.org, Todd Fahrner <fahrner@pobox.com>
My view is the same as Douglas' on this issue.  The behaviour of IE3 was
a bug - well, limitation of the way we chose to implement CSS, actually.
IE4 does not have this limitation - CSS rules or inline styles that
apply to a FONT tag will override the FONT tag properties, but the font
tag is not overridden by inherited stylesheet properties.

Chris Wilson

> -----Original Message-----
> From:	Douglas Rand [SMTP:drand@sgi.com]
> Sent:	Friday, August 01, 1997 1:32 PM
> To:	David Perrell
> Cc:	www-style@w3.org; Todd Fahrner
> Subject:	Re: CSS vs. transitional markup [was: No Subject]
> David Perrell wrote: 
> > Does IE honor stylesheet attributes for FONT over inline ones? FONT
> is
> > an element like any other. When its inline style attributes are not
> > overridden by a CSS declaration, shouldn't those attributes override
> > the parent?
> In our browser,  the FONT declarations would override the parent.
> CSS1
> decls for the FONT tag itself would first be honored,  then the
> attributes.  I treat attributes in essentially the same fashion as a
> STYLE attribute.
> So my view is that indeed the inline attributes of the FONT should
> override the parent.  For my own implementation it also means that the
> style object associated with FONT and any children's style object
> inheriting cannot be cached.  Ah well.
> Doug
> -- 
> Doug Rand				drand@sgi.com
> Silicon Graphics/SSO			http://reality.sgi.com/drand
> Disclaimer: These are my views,  SGI's views are in 3D
Received on Monday, 4 August 1997 12:22:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:26:44 UTC