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

embedding 3.0-compatible markup (was [No Subject] (fwd))

From: Sho Kuwamoto <skuwamoto@macromedia.com>
Date: Fri, 1 Aug 1997 11:46:39 -0700
Message-Id: <v03007804b007dc952a10@[192.168.65.140]>
To: www-style@w3.org
MegaZone <megazone@livingston.com> wrote:
>Once upon a time Josh Paluch shaped the electrons to say...
>>I notice that in IE4 stylesheets don't trump <font> and <basefont>... is
>>this by design?  (at least on windows)
>>
>>Of coarse, Netscape4 does just the oppisite (ie, if the same element is
>>defined by both CSS and <font>, then CSS wins, even if <font> is closer
>
>In this case I like the NS method better.
>
>It allows an author to use the old hacks for a while and still move up to
>CSS for newer users.

This problem might be alleviated if there were a way to control
the behavior of the font tag from within CSS. Imagine:

<STYLE>
  .fancy { font: 16pt/18pt Garamond, Times, serif }
  font { disabled: true }
</STYLE>

<H1 class="fancy"><font yadda yadda>Some stuff here</font></H1>

Of course, this isn't a good general solution, because it entails
turning off a tag globally, which may not be practical for tags
like the <b> tag. Another solution might be to have a "if no styles"
attribute which functions much in the spirit of the <noframes>
tag. It would allow one to embed formatting information which only
renders on non-styled browsers.

<H1 class="emphasized"><B nostyles>Stuff in here</B></H1>

Thoughts?

-Sho
Received on Friday, 1 August 1997 14:36:27 GMT

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