New issue
Advanced search Search tips

Issue 706519 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-04-13
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

tab-specific touchpad scrolling breakage

Project Member Reported by grt@chromium.org, Mar 29 2017

Issue description

59.0.3054.0 (Official Build) canary (64-bit)

I don't know how it managed to get into this state, but I had one single tab for which trackback scrolling (two-finger scrolling on a ThinkPad P50) stopped working. All other tabs in the same and in other browser windows worked just fine. Refreshing the tab didn't help. Killing it and opening a new one did.

Is there some "i'm scrolling" state for a tab that can somehow get out of whack?

CCing a few people who may know where to look and spamming a few labels. Please reply with suggestions on how to debug if it happens again. Thanks.
 

Comment 1 by grt@chromium.org, Mar 29 2017

"trackback" -> "trackpad", of course
Cc: dtapu...@chromium.org sahel@chromium.org
Labels: Needs-Feedback
NextAction: 2017-04-13
sahel@ any ideas?

More details on the page that you were on might help us. But really a reproduction step would be awesome. 

Are you able to grab a trace when it is in this state?

Comment 3 by sahel@chromium.org, Mar 30 2017

Can you reproduce the bug when smooth-scrolling is disabled? There are some cases that smooth scrolling is enabled and you scroll while navigating to another page, or switch from cc to main for scroll handling and after that scrolling freezes for the tab: 704410, 689661


Comment 4 by grt@chromium.org, Apr 4 2017

I think I had a rietveld issue loaded in the no-touch-scrolling tab. Scrolling via arrow keys and the scrollbar worked fine. I'll grab a trace if it happens again. Thanks.
grt@ can you verify this is working against Canary. This sounds like  issue 704410  which is now fixed.
ping grt@ we believe this is fixed but we just want confirmation you don't see it anymore.

Comment 7 by bokan@chromium.org, Apr 19 2017

Status: WontFix (was: Untriaged)
FYI:  issue 704410  didn't get pushed into 57 so you won't see it yet. But 58 is currently being pushed out and should include the fix.

I'm going to close this as it sounds very likely to be 704410 and we haven't heard back. Feel free to reopen if you don't think that's the case.

Sign in to add a comment