Caret issue on mobile chrome leading to incorrect input about v-mask

[jontybrook]

I'm also seeing this. Using v-mask="'£######'", all works fine on desktop but in Chrome on mobile the first character flips infront of the subsequent chars. Eg entering "1234" results in "2341".

[shrpne]

Looks like only Samsung devices affected by this issue. I have tested with Galaxy s5 mini.
Other devices with chrome works fine for me

[paraboul]

@shrpne this is related to the Chrome version. Currently testing on an updated chrome on Android O (e.g. Google pixel)

[luiztsmelo]

Same here, using a Xiaomi device and chrome 61. But using an Asus device with chrome 61 works fine.
Can't we do anything about it?

[tonpereira]

Hello, I'm having the same problem on Chrome mobile, and on Android 8 ..
Has any solution been found for this bug?
a field with mascara 000.000.000 and in time to appear the "." the mouse cursor goes to before the next digit, after the ".".

[probil]

Seems like related to #41

[lndsy-cherry]

I'm experiencing this issue as well. According to issue 41, it looks like this has been going on for a while. Any updates @probil? V-mask has worked so well up until this point!

[probil]

@lndsy-cherry I will try to reproduce and fix today (approx. in an hour)

[lndsy-cherry]

Thanks so much for the quick reply!!

[probil]

@lndsy-cherry I can't reproduce it on my android phone. :(
Could you please check the fix on your device? It's not yet published on npm so you need to install v-mask this way:

npm i probil/v-mask#feature/fix-caret-on-mobile-chrome

Please, let me know about the result of the testing.

[lndsy-cherry]

@probil I just tested and that fix worked like a charm! Please merge and thank you so much again for this! :)

[probil]

Fixed in v1.3.2. Thanks everyone.

[lndsy-cherry]

@probil it looks like some Android+Chrome devices are still experiencing an issue (I was testing on a Galaxy S5 earlier and noticed some cursor movement when typing a simple mask like ###-###), though it seems like there is no issue on an emulated Android+Chrome experience.

I see in your code you're using initEvent in the trigger function, yet this looks to be a deprecated feature (https://developer.mozilla.org/en-US/docs/Web/API/Event/initEvent). I'm wondering if this may be affecting this. Would you have any plans to update the event triggering used?

[probil]

@lndsy-cherry
That code was borrowed from vue core. But thanks for letting me know.
Let's discuss in the separate issue. Could you please create it?