W3C home > Mailing lists > Public > www-html@w3.org > February 2000

Re: inline CSS (was: is anyone interested in XHTML?)

From: Håkon Wium Lie <howcome@opera.com>
Date: Tue, 22 Feb 2000 11:42:57 +0100 (Romance Standard Time)
Message-ID: <14514.26673.890000.838495@ETTE>
To: Murray Altheim <altheim@eng.sun.com>
Cc: www-html@w3.org
Also sprach Murray Altheim:

 > !important fails in that it requires that a user somehow has available on 
 > their machine a stylesheet tailored to their particular needs

That's right. A style sheet tailored to their particular needs.

 > that this 
 > stylesheet somehow can override the author's stylesheet (which means that 
 > it can magically attach to any document, no matter which ML), that they
 > somehow would have previous access to the document's markup in order to 
 > know *what* to override

True, that's why we have a limited set of HTML elements.

 > With XML's lack of fixed vocabulary this is
 > clearly useless

No. Consider:

  * { color: black; background: white }

But you are right in pointing out that generic XML on the web raises
accessibility concerns.

 > >  > I clearly see a pattern of CSS people doing whatever they can to proliferate
 > >  > CSS into every damned spec coming out of the W3C,
 > > 
 > > I find your language offensive. W3C is naturally interested in reuse
 > > and synergy between its specifications.
 > I don't think forcing a vector graphics specification to use styling is 
 > exactly "reuse", and the presence of the SVG minority report would tend 
 > to confirm my opinion.

I think a style sheet language makes perfect sense in vector graphics.
It lets you make all door handles red in one operation, or give them
the same color as the headings in your document. The issue in the SVG
seems to be that some vendors want a final form format rather than a
restylable, reusable one.

 > There's a vocal feedback on both sides of the aisle, and I expect there
 > always will be.  I've heard all manner of argument for and against frames,
 > too. I always expect that you and Chris and Bert are going to argue in 
 > favor of inline styles, just as we all did in 1995. You guys always seem 
 > to gloss over all the problems that this implies for WAI, i18n, and now 
 > document transformations. 

What problems does the STYLE attribute create for and WAI, i18n? I'm
aware that XSLT isn't suited for dealing with the STYLE attribute.



Chief Technology Officer                                Opera Software
Håkon Wium Lie                     http://www.opera.com/people/howcome
howcome@opera.com                                gets you there faster
Received on Tuesday, 22 February 2000 05:35:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 30 April 2020 16:20:39 UTC