Phone input cursor jumps to end

Hi @Tess ,

I am facing this same issue when using the phone number input field. Any update on the fix? Any workaround available?

Thanks,

Sarah

Hi Sarah,

It looks like the phone input jumps to the end if you exceed the number of digits per section. For example,

If your US zip code is 2 digits, 45, you can go back and add a 1 in between (to make415), and the cursor won't jump to the end. As soon as you add another digit, making the input 4115, a space gets added between 411 and 5, and the cursor moves to the end.

Is that what you're seeing as well? I believe this is the intended behavior, but I can put a request in our backlog to maintain cursor position

I think I'm seeing something a little bit different. Here's an example:

lets say I entered the following phone number incorrectly
what I typed: 1 973 222 2222
the correct number: 1 973 212 2222

when I place my curser to erase the 2 and replace it with 1, my curser jumps to the end as soon as I erase the 2 - see below

image
image

:+1: Thanks for this example! Highlighting the 2 you want to change and typing a new digit to replace it seems to have more of the expected behavior (but end users may not take that approach!). I am sharing this feedback with the team. I think both of our examples are ultimately related, and it's worth investigating whether we can ship a fix.

1 Like