Different masking behaviour on Android

[andregoncalvesdev]

Describe the bug

I am having different masking behaviour on android/chrome. Simply typing 100 and then 1.

Tested on different devices and environments and it happens only on this specific version of chrome. Also, if we set the inputMode as numeric it doesn't happen.

Desktop

Bug.desktop.mp4

---

Mobile

bug.mobile.mp4

---

To Reproduce

https://codesandbox.io/s/quirky-goldstine-py3ths

Expected behavior

1001 -> 1,001 on both.

Environment:

• Device: Pixel 7
• OS: Android
• OS version: 13
• Browser: chrome
• Chrome Version: 111.0.5563.58
• react-imask version: ^6.4.3

[ArmanNisch]

I can confirm I am also seeing this behaviour. It's actually any number that one types after 100 with x.

So type 100, wait two seconds, type 1, then one gets 10,011,001
Type 100, wait two seconds, type 2, then one gets 10,021,002
Type 100, wait two seconds, type 3, then one gets 10,031,003
Type 100, wait two seconds, type 4, then one gets 10,041,004
Type 100, wait two seconds, type 5, then one gets 10,051,005

This issue also only seems to happen on the 100 number. I tried 200 x, 300 x, 400 x, etc. and all seemed fine.

[pangolingo]

I've also observed this issue. We worked around it by using inputmode="numeric", which does seem to resolve the problem.

I noticed that typing 100 and then non-numbers (q, m, etc) will also add extra digits to the input.

Environment:

Device: Pixel 5a
OS: Android
OS version: 13
Browser: chrome
Chrome Version: 112.0.5615.135
react-imask version: ^6.4.3

[ArmanNisch]

Any update on this? :)