Re: Tabbed Interfaces in CSS

2009/4/24 Brad Kemper <brad.kemper@gmail.com>:
>
> On Apr 24, 2009, at 5:40 AM, Giovanni Campagna wrote:
>
>> First of all, read User Interface for CSS3 [1]. You'll find in section
>> 5.3.3 a property called "user-select", that defines the selection /
>> activation behavior for all elements, regardless of event handling
>> registered on them.
>> The value "toggle" says that activation (mouse click, enter key press)
>> should toggle the :checked pseudo-class, using the value of
>> "toggle-group": if the latter is "none", element is a checkbox, else
>> it is a radiobutton (only for :checked).
>>
>> This means that to your proposal you just need to add
>> "user-select: toggle" in the style for cards
>> (it may be implied by appearance:card, but I hope no, since it is not
>> implied by appearance:checkbox or appearance:radiobox currently)
>>
>> Adding this property would it be a problem for you?
>> If yes, why?
>
> User-select seems like overkill, unless it is genuinely useful beyond this.
> A click without a drag should be enough to toggle the radio button
> click-state.

Ehm... what does "click without a drag" mean? I can click on a radio /
checkbox button and drag, and it will check it (if I end my mouse
movement inside the button).
Besides "user-select" is very useful also outside of "toogle", for
example if you want to make your links act like push-buttons
(unselectable).
Really, I don't support your ":checked" on any element proposal: I
author, want to control which elements can be checked and which
cannot, and "user-select: toggle" is a good way to do it (not the only
one, sure, but an explicit declaration is necessary)

> 'toggle-group' by itself sounds pretty similar to what I had in
> mind for 'radio-group'.  'group-reset' does not seem necessary, and neither
> does the statement on that page about nesting and resets.
Forget "group-reset" (unless you want to put tabbed interfaces inside
tabbed interfaces and you want to reuse the same identifier, which may
be useful)

> The 'user-input' property on that page seems to go way beyond what is
> actually needed here. I would make 'nav-index' (nee 'tab-index') something
> that any element can have, but which defaults to 'none' for not previously
> enabled elements (i.e. non-form elements). Setting a LEGEND to 'nav-index:
> auto | <number>' would make it focusable.

Forget "user-input" as well. Just keep:

"user-select" : control the selection behavior
"user-focus" : control the focus behavior
"nav-index" : control the navigation (focus) order

I really prefer them to "nav-index" + nothing. At least the author is
aware of what is actually happening at his pages.

Giovanni

Received on Friday, 24 April 2009 22:42:38 UTC