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

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

From: Jelks Cabaniss <jelks@jelks.nu>
Date: Thu, 17 Feb 2000 19:40:07 -0500
To: <www-html@w3.org>
Message-ID: <NBBBICMNIPCICMKJECCBEEDIDGAA.jelks@jelks.nu>
Sue Sims pragmatically asked:

> > > On the rare occasion I need to override a rule from my external CSS...
> > > Let me <span> the silly thing and be done with
> > > it...please?

To which John W Pierce rather despairingly responded:

> > This is exactly right. Which, of course, almost without doubt means that the
> > spec will wind up disallowing it in some way.

Which Murray Altheim attempted to clarify:

> Simply because somebody likes frames or inline styling, or <blink> or
> <barf> doesn't mean we stick it in a specification. ...
>
> XHTML 1.0 is essentially *all* of HTML 4.0, so use it. XHTML 1.1 is a very
> functional subset of that, using a modular framework to allow for all sorts
> of extensions. Use HTML 4.01, XHTML 1.0 as you need to. Nobody is removing
> either from the playing field. XHTML 1.1 will be used for purposes other
> than perhaps than you find valuable. Fine. Don't use it.

Murray, are you saying XHTML 1.1 does *not* permit inline styling?  At

	http://www.w3.org/TR/xhtml-modularization/xhtml_modules.html#s_textmodule

it shows that most of the elements contain the "COMMON" attributes.  COMMON is
defined as Core + Events + i18n + Style.  It then adds:

	Also note that the Style collection is only defined when
	the Stylesheet Module is selected. Otherwise, the Style
	collection is empty.

So if you include the Stylesheet Module (which anyone wanting to use CSS would
do), don't you have inline styling capability in XHTML 1.1.  What am I missing?


/Jelks
Received on Thursday, 17 February 2000 19:42:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:42 GMT