You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When every inputs are empty, do select per default the first one, even if the one selected isn't the first one.
Use case
After analyzing the UX of such input fields, user aren't use to select the first one, but always click somewhere in the center and start to write.
For us, this will sort of always start with the first having to be selected before moving one to the next one.
Idea
I would add a new input field autoSelectFirstInput = true (default being true). SO if someone which they can deactivate this feature.
Default true : Because this is what make the more sense.
Then, on click -> if every inputs are empty -> select first one.
Extended
autoSelectFirstInput could be chance to autoSelectedInputIndex = 0. This would let the user select which one to autoselect. But I cannot see any use case for this.
The text was updated successfully, but these errors were encountered:
Description
When every inputs are empty, do select per default the first one, even if the one selected isn't the first one.
Use case
After analyzing the UX of such input fields, user aren't use to select the first one, but always click somewhere in the center and start to write.
For us, this will sort of always start with the first having to be selected before moving one to the next one.
Idea
I would add a new input field
autoSelectFirstInput = true
(default being true). SO if someone which they can deactivate this feature.Default true : Because this is what make the more sense.
Then, on click -> if every inputs are empty -> select first one.
Extended
autoSelectFirstInput
could be chance toautoSelectedInputIndex = 0
. This would let the user select which one to autoselect. But I cannot see any use case for this.The text was updated successfully, but these errors were encountered: