Re: Widgets within widgets

How does this influence tree controls (or similar list-like widgets)
that contain smaller widgets?

For example

A tree widget only has one of its nodes in the tab order at a time (the
last selected one). If each node in the tree contains smaller widgets
(for example, tristate checkboxes), I would expect only the smaller
widgets in the selected branch to become part of the tab order, but not
the smaller widgets in other opened branches. Your description makes it
seem as every visible smaller widget would be part of the tab order,
regardless of whether the node they're contained by is currently
selected and part of the tab order.

What would be the expected (or ideal) behavior here?

Regards,

Hans Hillen

Chris Blouch wrote:
> I was asked to write up a generalized statement as to how this should
> work as far as keyboard controls.
>
> CB
>
> -------
>
> Clarification on widgets within widgets
>
> The general navigation model is for a user to tab to a widget, interact
> with the controls in that widget and then tab to move focus off to the
> next widget in the tab order. By extension, when the construct of a
> widget contains another widget, tab will move focus to the contained
> widget because it is the next item in the tab order. This continues down
> the layers of widgets until the last widget is reached. For example: We
> have two widgets A and B on a page. Widget A contains within it Widgets
> C and D. When tabbing, focus would land on Widget A but another tab
> would not go to Widget B. Instead it would focus on C and then D
> followed by B.
>
>
>
>