Issue metadata
Sign in to add a comment
|
Unresponsive touch screen input on Microsoft Surface Go |
||||||||||||||||||||||||
Issue descriptionChrome Version: 71.0.3578.98 Stable OS: Win10 This does not reproduce on 73.0.3674.0 Canary. What steps will reproduce the problem? (1) Visit any page, e.g. chrome://version (2) Scroll or pinch-zoom using the touch screen. What is the expected result? Smooth scrolling. What happens instead? Input often becomes very unresponsive, with ~0.5 seconds between updates. See video. https://drive.google.com/file/d/1FOSQgcb8JDRYiEPu7pj4yqP5aiAHIKO6/view?usp=sharing I think it is input related, since pages that have CC or Main Thread animations continue to run smoothly while input is unresponsive.
,
Jan 18
(5 days ago)
ligimole@: can you assign someone here in 900 to do a bisecting on this? Apparently we already fixed the issue, so it's good to know which CL fixed the issue. I can bring over the device tomorrow.
,
Jan 18
(5 days ago)
Prudhvi, could you please give a try.
,
Jan 18
(4 days ago)
So far based on my testing on Microsoft Surface Go the issue is fixed on latest Chrome Beta that is 72.0.3626.64.
,
Jan 18
(4 days ago)
,
Jan 18
(4 days ago)
From bokan@, this looks likely to be a duplicate of Issue 871257 .
,
Jan 18
(4 days ago)
This is likely issue 871257 - the fix landed there at 72.0.3595.0 so that's consistent with #4 - you may want to just confirm the version prior is still regressed.
,
Jan 18
(4 days ago)
The fixing CL is indeed in that range
,
Jan 18
(4 days ago)
#7 indicates the fix is a different CL from the fix for 871257
,
Jan 18
(4 days ago)
Based on manual bisect I see that the scrolling was very unresponsive until Chrome version 72.0.3592(broken) and starting working normally since 72.0.3593.0(Fixed). Bisect range : https://chromium.googlesource.com/chromium/src/+log/72.0.3592.0..72.0.3593.0?pretty=fuller&n=10000 Note : Still trying to get the python script on the tablet and will update once I am successfully setup.
,
Jan 18
(4 days ago)
More specifically it looks like the fix landed in 72.0.3593.0. I think that is in the range. https://storage.googleapis.com/chromium-find-releases-static/69f.html#69f83ca4122cc656480439d58afa0d2f656e3dc5
,
Jan 18
(4 days ago)
Never mind. The fix is between 72.0.3592.0 and 72.0.3583.0. So it seems it is a dupe of 871257.
,
Jan 19
(4 days ago)
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vmi...@chromium.org
, Jan 18 (5 days ago)