# 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:** 6

<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 februari 2019 om 14:24 UTC](https://meta.discourse.org/t/looking-for-some-clarity-on-the-android-chrome-touch-offset-issue/109027/6 "2019-02-13T14:24:17Z")

</div>

> [@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.

---

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