Ticket #1739 (new bug) — at Initial Version
TAB_NAVIGATION_BEHAVIOR
| Reported by: | dido | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | M12_RELEASE |
| Component: | INTERACTIVITY_COMMONS | Version: | 2.0 |
| Keywords: | tab | Cc: | |
| Category: | END_PROD | Effort: | |
| Importance: | Ticket_group: | ||
| Estimated Number of Hours: | Add Hours to Ticket: | ||
| Billable?: | yes | Total Hours: | |
| Analysis_owners: | Design_owners: | ||
| Imp._owners: | Test_owners: | ||
| Analysis_reviewers: | Changelog: | ||
| Design_reviewers: | Imp._reviewers: | ||
| Test_reviewers: | Analysis_score: | 3 | |
| Design_score: | 0 | Imp._score: | 0 |
| Test_score: | 0 |
Description
When navigating with TAB key in the application the focused component is not always visible.
- If, for example, a HUD is opened (Change border and background), then a text input is focused.
- After filling the data and pressing tab few times, no component is visibly focused.
- Components that can't be manipulated via keyboard should be missed in the tab order. Or keyboard manipulation should be enabled for them as well as visible focused state.
- Also when user is focused on one HUD, the tab order shouldn't include elements outside this HUD.
- One other thing is that when the focus is set via tab button on the text input, it doesn't select the content, instead just set the pointer at the end. This should select the entire content in the text input.
Note: See
TracTickets for help on using
tickets.
