Bug with cursor position on Google Pixel v7.1.2 after new release

[s-yadav]

Bug with cursor position on Google Pixel v7.1.2 after new release

[theseanz]

I'm having this exact problem with version 1.0.1 on a Nexus 5X and our QA's Samsung S6. I updated to 1.0.2 and it seems to have fixed it on my Nexus 5X, but version 1.2.0 does not work.

[pudgereyem]

I've investigated this a bit, and it seems like let cursorPos = el.selectionStart; in the onChangeHandler returns the wrong thing. So after I write for example 4 in the input, cursorPos is still set to 0.

This works however on 1.0.2, where refs where being used.

It happens on my device Google Pixel 7.1.2

Thoughts @s-yadav ?

[s-yadav]

@pudgereyem Hey could not reproduce this on browserstack can you try the alpha version again ?

[pudgereyem]

Hi @s-yadaw, I just tried on the Codepen demo and still same error. I can have a look at the changes today.

I get that it's frustrating to not be able to test the version I've reported as not working. Would be nice if we could find a solution. I'll have a look soon.

[s-yadav]

Browserstack does have real device testing but can't reproduce it there either.
Have you installed some custom keyboard on your device?
Also try the codepen again by clearing cache just to make sure old code not been cached.

[pudgereyem]

@s-yadav

Yes, it works in Browserstack for me too. But not on my actual phone. I wonder if it's the same version (7.1.2). Browserstack only say (7.1). I've also cleared the cache, didn't help.

Recording

I pulled down the project, using 2.0.0-alpha2, and recorded both my phone, and the Chrome Console (Remote testing).

I also added two lines of code that's logging cursorPosition in onChangeHandler. See screenshot; http://pudge.se/gEraYU

• Google Pixel 7.1.2: http://pudge.se/bWrX6s
• Remote Device Inspect: http://pudge.se/ci6rR

Takeaways

1. On first input, the cursorPos is wrong. It returns 0 when it should be 1
2. On first input, the character inputed gets underlined, see screenshot; http://pudge.se/81EVaA
3. On first input, the keyboard layout is changed, why? see screenshot; http://pudge.se/81EVaA

[pudgereyem]

Based on the takeaways in my comment above, I did some testing.
When changing the type to tel it works. I'm not sure why, I'll investigate this more.

ping @s-yadav

[s-yadav]

I guess it has do with your soft keyboard you are using.
Are you using any other keyboard app than native one ?

[pudgereyem]

@s-yadav I use the native keyboard. What do you mean with "soft keyboard"?

[s-yadav]

The mobile keyboard. Can you try logging el.selectionStart and el.selectionEnd on onChange handler.

[s-yadav]

@pudgereyem Can you try alpha3 build once? I hope that's the possible fix for pixel.

[s-yadav]

Fixed in 2.0.0 alpha

[pudgereyem]

Hi @s-yadav, this issue went away if you used type="tel".