Grid support for standard keyboard selection and navigation

[drschwartz]

The standard Windows keyboard techniques for navigation and selection of objects within a container should be implemented by Grid. Mimic Windows Explorer behavior re effects of Up/Dn (focus moves to previous/next objects, respectively), CTRL+Up/Dn (leave selection and move input focus), ENTER (default action, e.g Open), CTRL+click (toggle selected state of object clicked), SPACEBAR (selects object with input focus), SHIFT+ Up/Dn (extend selection), etc. This will allow keyboard users to apply the same techniques regardless of context, desktop or Web applications.

[bill]

Looks like a dup of #7286.

BTW grid bugs are filed with component "DojoX Grid" since grid isn't part of dijit (yet).

[drschwartz]

I read #7286. It's not a dupe of this ticket. That ticket addresses a problem when navigating too quickly with cursor keys. This ticket is about full support of keyboard navigation and selection including augmenter keys, e.g., CTRL.

Re-categorized component is fine

[bill]

Note from Becky: see http://dev.aol.com/dhtml_style_guide#grid and http://lists.w3.org/Archives/Public/wai-xtech/2008Aug/0133.html (which is an ongoing discussion).

[becky]

Note that selection must be visible in Windows high contrast mode as well.

[drschwartz]

- I assume that SPACE selects the cell currently with the focus?

- Are tabs consumed by input fields and text areas? If so, how does the user tab out? CTRL+Tab and SHIFT+CTRL+Tab?

- RE the following statement: Why would it take the focus on the first cell in the table? Is that what is intended?

"Once the focus is on the grid itself, any left, right, up, or down key takes the navigation focus to the position 1,1 in the grid regardless it is a simple or complex, unified or non-unified grid."

- What is the effect of CTRL + Home/END in Actionable mode? I would think it would move the focus to the first/last actionable item in the first/last cells, respectively.

- RE the appropriate behavior of F2 (whether it's a toggle), there's nothing to stop a grid cell from containing another grid, correct? If so, then F2 needs to be reserved to move into actionable mode for subordinate grids, right? That is, it's not a toggle (and behaves like Windows XP Explorer).

[peller]

moving 1.4 open tickets to 1.5