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


From: Matthew Brealey <webmaster@richinstyle.com>
Date: Wed, 03 May 2000 11:43:52 -0700
Message-ID: <39107368.52A6@richinstyle.com>
To: www-style@w3.org
L. David Baron wrote:
> On Tue, 02 May 2000 15:02:29 -0700, Matthew Brealey
> (webmaster@richinstyle.com) wrote:
> >
> > 2. For activatable elements, the :active period is not the same as the
> > CSS definition of :active in most UAs. For example, once buttons have
> > been 'pressed', they should have an outline. This persists until any
> This outline could be considered to be present because the elements
> match :focus.  I think MSIE for Windows interprets :active as the same
> as :focus (although it doesn't implement :focus, I don't think).
> However, the Netscape meaning of :active (matches while the element is
> *being* activated) differs from :focus, and Mozilla/NS6 implements the
> outlines as coming from :focus (which makes sense to me, especially
> when tabbing through links / forms).
Although this is true, the definition of :focus is that the element
accepts user input. A clicked-on button does not accept user input (you
can't select it again without tabbing to it or clicking on it), and does
not fall into any of the pseudo-class states.

PS. Re: BeCSS? Sorry: UI WD
Received on Wednesday, 3 May 2000 06:39:03 UTC

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