Matthew Brealey wrote:
> L. David Baron wrote:
> >
> > On Tue, 02 May 2000 15:02:29 -0700, Matthew Brealey
> > ( 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.

A button does accept user input since you can press space to re-click it.
However I think this could be solved in a nicer way using my proposal of a
:default pseudo-class (section 4 in my mail "Extensions to CSS3 selectors").
The class would match the element that is activated when the user press
enter (or whatever action is used as "activate" on the platform).

An example:
<form action="page1.cgi"><input name="text1"><input type="submit"
<form action="page2.cgi"><input name="text2"><input type="submit"

the :default pseudo-class would match the "button1" button when "text1" or
"button1" had focus. But would match "button2" when "text2" or "button2" had

/ Jonas Sicking

Received on Wednesday, 3 May 2000 17:52:13 UTC