W3C home > Mailing lists > Public > www-style@w3.org > January 2013


From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 14 Jan 2013 21:33:06 +0000
To: Håkon Wium Lie <howcome@opera.com>, "Jens O. Meiert" <jens@meiert.com>
CC: Reece Dunn <msclrhd@googlemail.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178291BF41586@TK5EX14MBXC221.redmond.corp.microsoft.com>

[Håkon Wium Lie:]
> Also sprach Jens O. Meiert:
>  > > I am interested in being able to specify WAI-ARIA markup in CSS.
>  > >
>  > > The aria properties should cover semantics not currently specifiable
> > > in CSS;  >  > Why? CSS’s purpose is not to add meaning (semantics).
> True, CSS is about styling. But the CSS syntax is quite handy for
> attaching any type of property/value pairs on elements.
Indeed, and it remains my favorite 'old IE' feature: unknown CSS properties
are added to the selected elements' style as string values i.e. if you write:

.custom {
	foo: bar;

Then all the elements with class custom get a foo property added to their style 
object with value "bar". No JS needed. Some will argue this should not be part
of CSS on semantic  grounds; the result is that some selectors live in 
stylesheets and many others are written in code, with changing one sometimes
requiring updating the other. I'm not sure what's so obviously better about that.
Received on Monday, 14 January 2013 21:34:17 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:23 UTC