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

Re: [CSS3] UI element states pseudo-classes

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Sun, 09 Jan 2005 21:31:08 +0100
Message-ID: <41E1948C.7080101@students.cs.uu.nl>
To: Andrew Fedoniouk <news@terrainformatica.com>, www-style@w3.org

Andrew Fedoniouk wrote:
> | CSS3 does define the :valid and :invalid attributes:
> |
> | http://www.w3.org/TR/2004/CR-css3-ui-20040511/#pseudo-validity
> |
> | When to match such pseudo-classes is of course up to the user agent. But
> | that is basically valid for all CSS selectors.
> 
> This is a good and symptomatic example.
> See, even in CSS spec. itself there are no one place where you can define 
> all selectors.
> http://www.w3.org/TR/2001/CR-css3-selectors-20011113/ defines one set with 
> :checked (sic!)
> and UI module defines one more set (specific for XForms).

Well... I agree it is somewhat inconvenient to not have all selectors in 
one place, but because of the modularization and the fact that one 
module can be completed before the other is, it cannot be avoided, I 
think. I'm not really bothered by that, though.

In any case, one of the things CSS is aiming for (er, from what I gather 
at least) is to be able to express the entire styling of a document by 
CSS alone (or at least, mostly), you should keep that in the back of 
your mind. These pseudo-classes are part of that. The UA controls 
whether a checkbox changes state from checked to unchecked, but you 
should be able to express the visual feedback of that by CSS alone. If 
you want to change the looks of checkboxes on your site, ditto.

If you look at the html stylesheet which can be found in e.g. Mozilla, 
you're already looking at a basic version of that.


~Grauw

-- 
Ushiko-san! Kimi wa doushite, Ushiko-san!!
Received on Sunday, 9 January 2005 20:31:12 GMT

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