New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 650271 link

Starred by 1 user
Status: Duplicate
Merged: issue 613808
Owner:
jsc...@chromium.org
Closed: Apr 2017
Cc:
dtapu...@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Two-finger scrolling stops working after resuming from sleep

Reported by raymond....@gmail.com, Sep 26 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Windows 10 Surface Book
2. Open Chrome, open new tabs with multi page content, two finger scroll through
3. Let laptop go to sleep
4. Resume from sleep

What is the expected behavior?
Two-finger scrolling continues to work on all tabs as it previously worked.

What went wrong?
Two finger scrolling no longer works. The screen bounces as though it only has a single page. If I create a new tab it works fine. If I duplicate the tab (same as creating a new tab really) it works fine.

No other program in Windows experiences this issue.

Did this work before? N/A 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by brajkumar@chromium.org, Sep 27 2016

Cc: brajkumar@chromium.org
Components: -UI Blink>Scroll
Labels: Needs-Feedback
Unable to reproduce this issue on Dell Precision M3800 using chrome latest stable M53-53.0.2785.116 by following steps mentioned in the original comment. Observed no issues in two-finger scrolling.

raymond.bennett@ - Are you able to reproduce it on incognito mode as well? Could you please confirm is this issue specific to surface pro?

Comment 2 by dtapu...@chromium.org, Sep 29 2016

Cc: dtapu...@chromium.org
Owner: jsc...@chromium.org
Status: Assigned (was: Unconfirmed)
jschuh@ I personally can't repro this on my windows 10 surface book. But I'm wondering if it is related to  issue 613808

Comment 3 by raymond....@gmail.com, Sep 29 2016 

@dtapu I just tried the repro steps in 613808 and I agree that it looks and feels exactly like the same bug. I am willing to have this closed as a duplicate of that one, and reopen if it is not resolved after fixing 613808.

Comment 4 by dtapu...@chromium.org, Apr 26 2017

Mergedinto: 613808
Status: Duplicate (was: Assigned)
►

Sign in to add a comment