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

Re: Tabbed Interfaces in CSS

From: Giovanni Campagna <scampa.giovanni@gmail.com>
Date: Fri, 24 Apr 2009 21:33:38 +0200
Message-ID: <65307430904241233r76d6080we98d3472f01aaff2@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>
We started from the proposal for tabbed interfaces that was in
Advanced Layout (before it was renamed to Template Layout). Slowly it
developed into a proposal for Advanced User Interface Module and,
basically, the ability to "check" any element by clicking in it (or
pressing return while focused).
That "checking" should set the :checked pseudo-class and remove any
:checked pseudo-class on element that belong to the same "radio-group"
/ "toggle-group" (set by the appropriate property).
I initially argued for "binding", later for "user-select", to avoid
the over-generalization of this behavior.

2009/4/24 Boris Zbarsky <bzbarsky@mit.edu>:
> Brad Kemper wrote:
>>
>> On Fri, Apr 24, 2009 at 10:51 AM, Giovanni Campagna     > I don't
>> understand your point. First you say you "don't support your
>>     > ":checked" on any element ". Then you say "UAs should anyway keep
>>    track of
>>     > :checked for every element", which seems to be the opposite point
>>    of view.
>>
>>    Actually, the first sentence is the result of the second: "I don't
>>    support your proposal because the UA would have to keep track etc."
>>
>> I see. I wouldn't think that would be burdensome on the UA, but perhaps an
>> implementer can chime in about that.
>
> I have to admit I've been mostly mass-deleting this thread.  What's the
> context here?  What proposal are we discussing?
>
> -Boris
>
>
Received on Friday, 24 April 2009 19:34:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:46:58 GMT