You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A team is interested in having a context/overflow menu in a tree, to allow the addition of new folders, deletions, renaming, etc.
Since context menu is not something easily invoked on a mac keyboard, they have been exploring using right arrow to provide access to an overflow menu inside a tree node.
For end nodes, this would seem to be conflict-free, since right arrowing on an end node has no current action.
For a parent node, right arrow has an action. However, right arrow on an open parent node has an action which I would call a redundant action. All it does is move to the first child node of the parent, which can also be accomplished with a down arrow.
I'd like to find out reactions to the model this team is proposing. Currently, the guidance in the APG reads:
Right arrow:
When focus is on a closed node, opens the node; focus does not move.
When focus is on a open node, moves focus to the first child node.
When focus is on an end node, does nothing.
The interaction with their variant would be something like:
Right arrow:
When focus is on a closed node, opens the node; focus does not move.
When focus is on a open node, moves focus to the first child.
When focus is on an end node, moves focus to child, if one exists.
This is somewhat connected to discussions like w3c/aria#1120
The text was updated successfully, but these errors were encountered:
A team is interested in having a context/overflow menu in a tree, to allow the addition of new folders, deletions, renaming, etc.
Since context menu is not something easily invoked on a mac keyboard, they have been exploring using right arrow to provide access to an overflow menu inside a tree node.
For end nodes, this would seem to be conflict-free, since right arrowing on an end node has no current action.
For a parent node, right arrow has an action. However, right arrow on an open parent node has an action which I would call a redundant action. All it does is move to the first child node of the parent, which can also be accomplished with a down arrow.
I'd like to find out reactions to the model this team is proposing. Currently, the guidance in the APG reads:
The interaction with their variant would be something like:
This is somewhat connected to discussions like w3c/aria#1120
The text was updated successfully, but these errors were encountered: