Skip to main content
User Experience

Return to Answer

replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

Only grab Tab for the field after something has been typed. This way navigating the page with keyboard shortcuts won't break.

Also give the user a clue as to what's going on, otherwise the behaviour may seem rather erratic. Provide some feedback that tab is now locked for indenting instead of form field navigation. Koen Lngeveen's answerKoen Lngeveen's answer has a good example of this, something like "Tab can now be used for indenting [release]".

Only grab Tab for the field after something has been typed. This way navigating the page with keyboard shortcuts won't break.

Also give the user a clue as to what's going on, otherwise the behaviour may seem rather erratic. Provide some feedback that tab is now locked for indenting instead of form field navigation. Koen Lngeveen's answer has a good example of this, something like "Tab can now be used for indenting [release]".

Only grab Tab for the field after something has been typed. This way navigating the page with keyboard shortcuts won't break.

Also give the user a clue as to what's going on, otherwise the behaviour may seem rather erratic. Provide some feedback that tab is now locked for indenting instead of form field navigation. Koen Lngeveen's answer has a good example of this, something like "Tab can now be used for indenting [release]".

Source Link
Ilari Kajaste
Ilari Kajaste
  • 364
  • 3
  • 12

Only grab Tab for the field after something has been typed. This way navigating the page with keyboard shortcuts won't break.

Also give the user a clue as to what's going on, otherwise the behaviour may seem rather erratic. Provide some feedback that tab is now locked for indenting instead of form field navigation. Koen Lngeveen's answer has a good example of this, something like "Tab can now be used for indenting [release]".