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

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

From: <mkirby@tappi.org>
Date: Fri, 1 Aug 1997 15:21:20 -0500
Message-Id: <199708011920.PAA10733@postal.atlanta.net>
To: skuwamoto@macromedia.com, www-style@w3.org
>>>>>>>>>>>>>>>
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>
<<<<<<<<<<<<<<<
This would require the browser developers to adopt this new css
attribute in their next version-- requesting that they adhere to an
agreed-upon method for CSS elements to supercede older presentation
elements (such as FONT and B) would stand just as much a chance for
success, IMHO.

>>>>>>>>>>>>>>>
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?
<<<<<<<<<<<<<<<
Perhaps this could be accomplished using the existing CSS spec, using the
class attribute? If it were possible, it would require a pretty tricky
stylesheet.

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

Regards,

Mike Kirby
Electronic Media Coordinator
http://tappi.org
mailto:mkirby@tappi.org
Received on Friday, 1 August 1997 15:20:26 GMT

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