W3C home > Mailing lists > Public > www-style@w3.org > September 1998


From: Braden N. McDaniel <braden@shadow.net>
Date: Thu, 10 Sep 1998 03:34:34 -0400
To: "Smith, Brooke" <Brooke.Smith@Butterworths.com.au>, "'Chris Lilley'" <chris@w3.org>
Cc: "'Chris Wilson'" <cwilso@MICROSOFT.com>, "'www-style'" <www-style@w3.org>
Message-ID: <002701bddc8d$74fae0e0$00808080@bonezero>
> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org]On
> Behalf Of Smith, Brooke
> Sent: Thursday, September 10, 1998 3:20 AM
> To: 'Chris Lilley'
> Cc: 'Chris Wilson'; 'www-style'
> Subject: RE: FONT vs CSS
> 	What you want - assuming you want valid CSS2, with the minor issue
> of
> 	actual implementation left aside for the moment ;-(  is
> 	font { font-family: inherit; color: inherit }
> Even when CSS2 browsers are out that support inherit, there will still be
> many CSS1 ones which don't and so this question will still need
> to be asked,
> though rather the actual question will be:
> "I use inherit to handle the problem of the FONT tag in CSS2
> browsers (FONT
> required for non-CSS browsers) but how do I handle FONT in CSS1 browsers?"
> Thus you see that inherit is nice but doesn't solve the problem.
> Our unfortunate position is that as Legal Publishers we have to cater for
> all those backward legal firms which are still using old computers and old
> browsers, and have a very thin upgrade policy.  And then some of the more
> technologically advanced ones do things like strip Javascript for security
> reasons (???).

Either satisfy yourself with a styleless (or "understyled") solution for
browsers that are not "CSS-aware", or forego CSS altogether. Or create a
script that will serve the appropriate version of the page based on the
browser/version. Unfortunately, that's what it comes down to.


Received on Thursday, 10 September 1998 03:32:35 UTC

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