# Touch offset issues on Android Chrome again

**URL:** <https://meta.discourse.org/t/touch-offset-issues-on-android-chrome-again/101404>\
**Category:** Product Support\
**Created:** [11월 6, 2018, 11:29오전 UTC](https://meta.discourse.org/t/touch-offset-issues-on-android-chrome-again/101404 "2018-11-06T11:29:37Z")\
**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:** [11월 7, 2018, 1:52오후 UTC](https://meta.discourse.org/t/touch-offset-issues-on-android-chrome-again/101404/6 "2018-11-07T13:52:38Z")

</div>

Looks like a Chrome Duet bug: [https://bugs.chromium.org/p/chromium/issues/detail?id=900843&q=component%3ABlink\>Input&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified](https://bugs.chromium.org/p/chromium/issues/detail?id=900843&q=component%3ABlink%3EInput&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified)

Workaround: Disable Chrome Duet in the flags.

---

_[View the full topic](https://meta.discourse.org/t/touch-offset-issues-on-android-chrome-again/101404)._
