Opened 15 years ago
Closed 15 years ago
#3304 closed defect (fixed)
first tree item should be in the tab order - not the tree container
Reported by: | Becky Gibson | Owned by: | davidb |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | Accessibility | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Currently the tree container element is in the tab order of the page. When the tree is created, the first tree item should be in the tab order rather than the tree container element. Only one tree item should ever be in the tab order at any one time. The last tree item with focus is the one which remains in the tab order. This way if someone tabs out of the tree control and then tabs back into the tree control, focus goes to the last tree item node accessed.
Attachments (5)
Change History (8)
comment:1 Changed 15 years ago by
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by
Changed 15 years ago by
Attachment: | 3304-move-focus.2.diff added |
---|
as before but removes tree root dom node from tab order.
Changed 15 years ago by
Attachment: | 3304-move-focus.3.diff added |
---|
Changed 15 years ago by
Attachment: | 3304-move-focus.5.diff added |
---|
fix for: 3304 3333 3335 (updated against a fresher trunk to resolve conflicts)
Note: See
TracTickets for help on using
tickets.
There are two approaches I'm thinking of: 1 - when a user tabs to the tree, automatically move focus to the first child 2 - programmatically set only the first child to be in the tab order
1 - is simple to implement. 2 - requires us to keep checking to make sure the first tree item hasn't changed (on add child etc.) and might be a bit heavy.
Both approaches have a bit of an odd smell to them.