# Android Chrome touch offset, 2020 editie

**URL:** <https://meta.discourse.org/t/android-chrome-touch-offset-2020-edition/161956>\
**Category:** Product Support\
**Tags:** mobile\
**Created:** [24 augustus 2020 om 17:05 UTC](https://meta.discourse.org/t/android-chrome-touch-offset-2020-edition/161956 "2020-08-24T17:05:11Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)\
**Post date:** [24 augustus 2020 om 17:05 UTC](https://meta.discourse.org/t/android-chrome-touch-offset-2020-edition/161956/1 "2020-08-24T17:05:11Z")

</div>

Continuing the discussion from [Looking for some clarity on the Android Chrome touch offset issue](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027/):

Found this old thread an decided to post an update.

- The Android Chrome touch offset is **definitely** still there, at least in our production environment ([Tappara.co](http://Tappara.co))
- I have searched for a solid repro pattern but this one is one hard nut to crack. It may be related to topic activity (new posts coming while typing a message) and possibly in combination with the users own actions - perhaps (accidently) scrolling the thread at the same time.
  - I have a gut feeling that this happened more likely during our on-season, when hockey games are live and topics are buzzing with chatter. Now during the pandemic (no games here) I have seen it less often.

The error is there, it is real, but a pattern is yet to be found. I see it few times a week on our site where I participate daily. Chrome, Android or Discourse updates have not resolved it. I have invested hours in finding a 90+% repro pattern, but no luck.

---

_[View the full topic](https://meta.discourse.org/t/android-chrome-touch-offset-2020-edition/161956)._
