feat: Set the cursor at the end of the input when autoupdating value

[Konixy]

When the input is empty and the user enters the first numbers, it auto insert the country code which is great, but the cursor is moved at the beginning of the input. That's very annoying because you must intentionally click at the end of the input to continue inserting your phone number.

Trying my best to be clear, hope it makes sense.

[gyurielf]

Hey! I'll look into it.

[agafonovim]

I've also encountered this issue! It's quite frustrating when typing a phone number - the cursor jumping to the beginning after the country code is auto-inserted breaks the natural flow of typing. You have to manually click or move the cursor to the end each time to continue entering the rest of the number.
This happens consistently when starting with an empty input field. I'm experiencing this with the following configuration:

const options: TelInputOptions = { 
  format: 'international', 
  invalidateOnCountryChange: true 
};

Would be great to have the cursor remain at the end position after the auto-update so users can continue typing seamlessly.

[gyurielf]

Thanks for the feedback, I try to fix it on this weekend. (I'm just pretty busy work and IRL things to do, so PR-s welcome)

[agafonovim]

@gyurielf No worries about the timeline! I understand you're busy.

I've already implemented a local patch for this issue that's working well. I'll clean it up and open a PR in the next few days to help out. This way you can review it when you have time, and it might save you some work this weekend.

The fix tracks when the input field is initially empty and ensures the cursor stays at the end when the country prefix is auto-inserted. Happy to discuss the implementation details in the PR if needed.

Thanks for the great library! 🙂

[gyurielf]

@agafonovim

I'd very welcome.

Thank you! I'd appreciate that.

Unfortunately nowadays I can't polish it as much as I want, so thanks for understanding.

BR!

[kpallado]

HI @agafonovim can you share the patch you did on this issue? just want to get some idea how to patch it locally