Looking for some clarity on the Android Chrome touch offset issue

[wewerewerewolvesonce]

Hi we’re getting some more reports of users not being able to select the reply box or being able to write in the reply field because of the cursor moving when trying to write/reply

I think something similar was reported here

Experiencing touch offset issues replying on Android

This topic tries to explain You start typing a reply and then at some point it seems like the box no longer recognises input properly. I find I can move the cursor around the input box but that’s it, no replies or anything. Seems to be resolved by either klling all apps and reopening Chrome (the reply is saved) switching to desktop and back I wondered if it might have been connected to the recent JavaScript fix done around making sure the topic auto-positioned in the right place? Otherwise…

and here

Touch offset issues on Android Chrome again

Continuing the discussion from Experiencing touch offset issues replying on Android: I’m sorry to inform that we have now received two separate reports on new issues which resemble recent problems fixed by Android Chrome version 68 something. They report that unlike before, they can write their posts as usual. However, they cannot hit the reply button on bottom left because of touch offset. The touch is registered just as you would react to a touch somewhere in the middle of the post. When the …

All people experiencing the issue are on Chrome 68+ the handsets are as follows: Samsung A3 and Pixel 3.

I have already had all users disable duet are there any other steps that we’re able to look at?

[codinghorror (Jeff Atwood)]

Do you have any specific repro steps? The issue was a Chrome bug in the past.

[wewerewerewolvesonce]

@codinghorror

Do you have any specific repro steps? The issue was a Chrome bug in the past.

Nothing too specific as I’ve not been able to repro it myself I’ll go back to the users.

[Falco]

The latest incarnation of the bug (the Duet one) was fixed in Google Chrome 72, which is the latest one. Make sure they are up to date.

[wewerewerewolvesonce]

I’ve had users disable duet and still have the issue would upgrading change this?

[Falco]

@wewerewerewolvesonce

I’ve had users disable duet and still have the issue would upgrading change this?

Well, it’s a Google bug and since Duet is:

1. A/B tested, so only a portion of users are affected
2. Can’t affect users using the full screen PWA for Discourse

I really don’t know. They broke this twice in a row so anything is possible.

[wewerewerewolvesonce]

I can ask everyone to upgrade their browser just in case, Is there a record of this bug that’s available elsewhere? I’m just wondering if there are any other published workarounds.

[Falco]

@wewerewerewolvesonce

Is there a record of this bug that’s available elsewhere?

The two topics you linked in the OP have links to the Google Issue Tracker.