# Experiencing touch offset issues replying on Android **URL:** https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086 **Category:** Support **Created:** [March 29, 2018, 12:51am UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086 "2018-03-29T00:51:39Z") **Posts on this page:** 10 **Page:** 3
### 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: [June 20, 2018, 12:25am UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/45 "2018-06-20T00:25:58Z")
![image](https://global.discourse-cdn.com/meta/original/3X/4/2/422f378981219596ad95a557ea79fcf6f4a695a6.jpg) Where the div is when you can’t click on it if you trigger the bug going up. It can be below too, if you go top → bottom. Also, I can repro this same behavior with the bottom bar on Instagram. After the first infinity scroll (when it loads more posts) the bottom bar will become inaccessible, depending on if the location bar is visible. ---
### Author: ![sgrif](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sgrif/32/119830_2.png) [@sgrif](https://meta.discourse.org/u/sgrif) #### Post date: [June 20, 2018, 2:07am UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/46 "2018-06-20T02:07:02Z")
![Screenshot_20180619-200627](https://global.discourse-cdn.com/meta/original/3X/0/d/0df517e5e3598c9d262b8c1c84b86c5d6dbbb861.png) ---
### Author: ![Info-Screen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/info-screen/32/119813_2.png) [@Info-Screen](https://meta.discourse.org/u/Info-Screen) #### Post date: [June 20, 2018, 6:56am UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/50 "2018-06-20T06:56:21Z")
Can reproduce too. Also fails for the post counter sometimes, though it works other times This thing: ![Screenshot_20180620-085910__01](https://global.discourse-cdn.com/meta/original/3X/6/a/6a79688f0e0720b2855999cb8eeaf65eaf9efbde.jpg) |Google Chrome|67.0.3396.87 (Official Build) (32-bit)| |OS|Android 8.1.0; ONEPLUS A5010 Build/OPM1.171019.011| ---
### 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: [June 22, 2018, 4:56pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/51 "2018-06-22T16:56:58Z")
Looks like someone was assigned this bug in Chromium. Let’s hope we can get a fix soon. ---
### Author: ![Osama](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/osama/32/98013_2.png) [@Osama](https://meta.discourse.org/u/Osama) #### Post date: [June 23, 2018, 7:09pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/52 "2018-06-23T19:09:31Z")
> [@Falco](#): > > Let’s hope we can get a fix soon. Looks like there is a fix in the oven, it’ll probably be pushed on Monday 🎉[https://bugs.chromium.org/p/chromium/issues/detail?id=848122#c34](https://bugs.chromium.org/p/chromium/issues/detail?id=848122#c34) ---
### Author: ![1101010](https://avatars.discourse-cdn.com/v4/letter/1/6de8d8/32.png) [@1101010](https://meta.discourse.org/u/1101010) #### Post date: [July 5, 2018, 11:10am UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/53 "2018-07-05T11:10:02Z")
FWIW I use Twitter on mobile not app and realise I’ve seen the same effect when retweeting: the browser was definitely registering my presses about 20 px lower than they were. ---
### 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: [July 9, 2018, 2:28pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/54 "2018-07-09T14:28:48Z")
This is [fixed](https://chromium.googlesource.com/chromium/src/+/4b32e5d123858b92e02524bff9a3ecc16ccd692e) in the latest Chrome Canary avaliable for Android (69.0.3486.0). It will be live in Chrome stable in ~10 weeks. ---
### 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: [July 25, 2018, 4:20pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/55 "2018-07-25T16:20:35Z")
Chrome 68 is live with the fix. I can’t repro this issue anymore. Google Chrome roll out is very slow on Android, so please check your current version before testing. ---
### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror) #### Post date: [July 25, 2018, 4:28pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/56 "2018-07-25T16:28:47Z")
---
### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror) #### Post date: [August 3, 2018, 9:31pm UTC](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086/57 "2018-08-03T21:31:16Z")
Definitely confirmed, just got the Chrome 68 update on my OnePlus 6 ![Screenshot_20180803-142907_2](https://global.discourse-cdn.com/meta/original/3X/a/3/a31cba83ccb31cff3b5ea6bc11bb27a86519630e.jpg) [Previous page](https://meta.discourse.org/t/experiencing-touch-offset-issues-replying-on-android/84086.md?page=2)