- From: Håkon Wium Lie <howcome@opera.com>
- Date: Mon, 21 Feb 2000 18:44:17 -0500 (EST)
- To: Murray Altheim <altheim@eng.sun.com>
- Cc: Tantek Çelik <tantek@cs.stanford.edu>, Jelks Cabaniss <jelks@jelks.nu>, www-html@w3.org
Also sprach Murray Altheim: > > far far ahead. and better for *usability* too, since CSS styling provides the > > user a mechanism to override with a user style sheet, which plain default HTML > > (or any markup for that matter) rendering does *not*. > > What nonsense. I keep hearing that, but CSS1 and 2 both have *author* as > priority, not user, so this runs completely counter to what would help > accessibility. As several people have pointed out, you're wrong on this. > 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. > even so far as to corrupt > XSL FO by reducing it to some common denominator of FO and CSS. You obviously were not present when the decision to align XSL FO with CSS was made. > Is there > some religous affiliation or stock options based on CSS or something? It's > like some mold that one can never clean out of the shower. Perhaps people just like it? I believe you should listen to the feedback from this forum and make sure the STYLE is present in XHTML 1.1 and future specifications. Having it in a style module along with the STYLE elment and the CLASS attribute makes sense to me. Regards, -h&kon Chief Technology Officer Opera Software Håkon Wium Lie http://www.opera.com/people/howcome howcome@opera.com gets you there faster
Received on Monday, 21 February 2000 18:49:01 UTC