New issue
Advanced search Search tips

Issue 922983 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Touch inputs in Chrome become unresponsive for ~5 secs after idle on one page

Reported by lasse1...@hotmail.com, Jan 17 (5 days ago)

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11151.113.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.127 Safari/537.36
Platform: chrome://version

Steps to reproduce the problem:
1. Stay on one page in Chrome for a certain amount of time
2. 
3. 

What is the expected behavior?

What went wrong?
Touch inputs become unresponsive for ~5 seconds on my Pixel Slate after staying idle on one Chrome page after an unknown amount of time (not too long, under an hour).

Did this work before? N/A 

Chrome version: 71.0.3578.127  Channel: stable
OS Version: 11151.113.0
Flash Version: 32.0.0.101 

Discovered when watching Twitch VoDs, which isn't exactly being idle, so it must just have to do with not doing any touch inputs. I have experienced it on other pages, including pages without video content.

The time it takes before touch inputs become unresponsive doesn't seem to be consistent, but I haven't used a timer or anything.
 

Comment 1 by lasse1...@hotmail.com, Jan 17 (5 days ago)

Also, this affects the entire device, so I can't pull up the shelf or anything either in those ~5 seconds.

But it does only happen when in Chrome, not Android apps.

Comment 2 by lasse1...@hotmail.com, Jan 17 (5 days ago)

Actually, it seemed like it happened in the YouTube Android app just now. But it felt shorter than 5 seconds. Not sure whether it was the same bug or not, but it's the first time I've noticed anything like it in an Android app.

Comment 3 by lasse1...@hotmail.com, Jan 17 (5 days ago)

It might actually have to do with how long a program/application has been open too, because I hadn't closed the YouTube app for a while.

That would explain why I'm experiencing it more in Chrome, because I never close Chrome. I'll need to test this further though.

Comment 4 by dtapu...@chromium.org, Jan 17 (5 days ago)

Components: Internals>Input>Touch>Screen

Sign in to add a comment