W3C home > Mailing lists > Public > www-style@w3.org > May 2009

Re: css3-selectors Summary of Comment

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 7 May 2009 19:24:34 -0500
Message-ID: <dd0fbad0905071724l28db7061v47fd89532e4397da@mail.gmail.com>
To: Janina Sajka <janina@rednote.net>
Cc: www-style@w3.org, "W3C WAI Protocols & Formats" <w3c-wai-pf@w3.org>
On Thu, May 7, 2009 at 7:02 PM, Janina Sajka <janina@rednote.net> wrote:
> Pseudoclasses:
> We ask that there be support for ARIA states and properties [1] as pseudoclasses.  Many of these are similar to things that are currently supported as pseudoclasses, in that they can be set in multiple ways.  For example, "checked" can be set from an HTML attribute, from aria-checked, or by user action.  It is useful for a CSS author to be able to style all checked things the same, regardless of how they came to be checked.   Ask whether the CSS WG thinks it's better to make that part of the selectors spec, part of the ARIA spec, or something else.  Is there an extensibility mechanism for psudoclasses.

There is no extensibility mechanism for pseudoclasses.  No particular
comment on the rest, though I suspect putting these extensions into
the ARIA spec would be best.

> Hover, active, focus:  All elements should be able to take those states.
> Any element that receives focus should be able to make use of those.
> With ARIA and with HTML 5, any element can be focusable.  Before that,
> form elements and buttons are also focusable.

CSS has no say on whether elements match these classes; it's entirely
up to the document language.  The CSS engines just need to know what
the document language wants.  As long as HTML5 and ARIA play nicely
together in this respect, we're great.

> ::before and ::after may offer a work-around to accessibility issues
> with generated content not being in the DOM.  PFWG thinks this is a
> useful feature and wants to see it supported.

I'm confused about what you mean by this.  ::before and ::after
*create* the generated content.  It feels like you might be thinking
that they let you *view* the generated content.  I'm not sure, though.

> What was the ::selection pseudo-element, and why was it removed?  From
> its name it seems it could be quite useful for ARIA-based applications,
> which manage their own selection.

::selection was supposed to contain "highlighted" text, like what you
produce when you click-drag your mouse across text, or click and
shift+arrow.  It was dropped because it's schizophrenic when you start
hammering down details, especially wrt inheritance.  It's hoped that a
reasonable treatment of it can be laid down in the future.

Received on Friday, 8 May 2009 00:25:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:26 UTC