# Looking for some clarity on the Android Chrome touch offset issue

**URL:** <https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027>\
**Category:** Product Support\
**Created:** [13 februari 2019 om 10:37 UTC](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027 "2019-02-13T10:37:51Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![wewerewerewolvesonce](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@wewerewerewolvesonce](https://meta.discourse.org/u/wewerewerewolvesonce)\
**Post date:** [13 februari 2019 om 10:37 UTC](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027/1 "2019-02-13T10:37:51Z")

</div>

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](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086):
>
> 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](https://meta.discourse.org/t/touch-offset-issues-on-android-chrome-again/101404):
>
> Continuing the discussion from [Experiencing touch offset issues replying on Android](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086): 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?

---

_[View the full topic](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027)._
