# 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 בפברואר,‏ 2019,‏ 10:37am 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:** 4

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [13 בפברואר,‏ 2019,‏ 2:18pm UTC](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027/4 "2019-02-13T14:18:12Z")

</div>

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.

---

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