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
For example if we want to type in the code 123456,
but we missed the 2 (maybe because the keyboard is not working properly), so instead, we type in 13456
We would have the field like this [1] [3] [4] [5] [6] [|]
then, we would try to correct it by clicking on the digit field with 3 in it
[1] [3|] [4] [5] [6] [] with | as cursor
since the 3 is now highlighted we want to replace it with 2.
if we type in 2, then the field state would be like this [1] [2] [4] [5] [6] [|]
the cursor jumps from the 2nd digit field to the unfilled digit
this might be frustrating for user since user has to go back again and again to the previous field to fill everything out.
While the user might be able to fully fill out the digits first, then go back and retype the wrong digits, it would be better experience if we highlight the next character, instead of the next unfilled field.
Expectation: [1] [3|] [4] [5] [6] []
if we type in 2 from this position
the state should be
[1] [2] [4|] [5] [6] []
and then type 3
[1] [2] [3] [5|] [6] []
so we can fill it in with 4, 5, and 6, completing the field.
The text was updated successfully, but these errors were encountered:
Btw... what if the value in a box not selected, but cursor are in a box:
Selected:
Value not selected, but cursor in the box:
** You can achieve this by pressing: Arrow Up, Arrow Down, Home, End, PgUp, PgDown keys, or using mouse.
What should happen in the second variant? For now pressing 2 digit doing nothing but just move cursor to the end. (Tested on MUI OTP Field home page)
Behavior that I can expect is that right part of value should be shifted, so the result should be next:
For example if we want to type in the code
123456
,but we missed the
2
(maybe because the keyboard is not working properly), so instead, we type in13456
We would have the field like this
[1] [3] [4] [5] [6] [|]
then, we would try to correct it by clicking on the digit field with
3
in it[1] [3|] [4] [5] [6] []
with|
as cursorsince the
3
is now highlighted we want to replace it with2
.if we type in
2
, then the field state would be like this[1] [2] [4] [5] [6] [|]
the cursor jumps from the 2nd digit field to the unfilled digit
this might be frustrating for user since user has to go back again and again to the previous field to fill everything out.
While the user might be able to fully fill out the digits first, then go back and retype the wrong digits, it would be better experience if we highlight the next character, instead of the next unfilled field.
Expectation:
[1] [3|] [4] [5] [6] []
if we type in
2
from this positionthe state should be
[1] [2] [4|] [5] [6] []
and then type
3
[1] [2] [3] [5|] [6] []
so we can fill it in with
4
,5
, and6
, completing the field.The text was updated successfully, but these errors were encountered: