Closed
Bug 1242854
Opened 9 years ago
Closed 4 years ago
[a11y] Improve keyboard access to right hand side inspectors from main markup view.
Categories
(DevTools :: Inspector, defect, P3)
DevTools
Inspector
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: yzen, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [btpp-backlog])
we want to tab to the right hand side panel from the current tree item after we reach last attribute by tabbing.
If we tab backward, and reach the very first item of the right hand side inspectors, the next tab should place the focus on the last attribute of the currently focused tag.
Comment 1•9 years ago
|
||
The current implementation makes the keyboard user navigate through the whole tree view by tab. A document with several hundred nodes and several attributes each easily means thousands of tab stops.
The way we want to change this is that tab only moves from the main tree view item (the tag) to its attributes and onwards onto the tab list of the right-hand side panel, and shift-tab in reverse order. The other tags can be reached via standard tree view arrow key navigation (p and down to switch rows, left and right to either skip to the parent node, or collapse or expand the current node if it has children, etc. So there is already a way to navigate to the different nodes via the keyboard, so the tab order can be shortened properly to easily reach the side panel without introducing extra keystrokes.
Comment 2•9 years ago
|
||
Triaging as P3 as not a current devtools team priority (filter on CLIMBING SHOES).
Priority: -- → P3
Whiteboard: [btpp-backlog]
Updated•6 years ago
|
Product: Firefox → DevTools
Reporter | ||
Comment 3•4 years ago
•
|
||
I think this can be closed, this behaviour is no longer a pattern with our tree widgets in the devtools and will probably be more confusing for our users. @Marco, would do you think?
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(mzehe)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•