TAB_NAVIGATION_BEHAVIOR

[dido]

When navigating with TAB key in the application the focused component is not always visible.

Example:

• a HUD is opened (Appearance HUD)
• Size box should be focused, there should be a cursor visible and you should be able to edit the number in the box via the keyboard
• After filling the data press TAB
• Focus should be moved to the next editable box but no component is visibly focused.

• components are editable but not seeing which one of them is actually focused makes it hard for the user to operate
• 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.

[deyan]

fixed