New issue
Advanced search Search tips

Issue 615822 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Rubber band

Reported by m...@christianburkert.com, May 30 2016

Issue description

Chrome Version       : 51.0.2704.63
OS Version: OS X 10.11.5
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Plugin in a USB cable mouse from Apple (e.g.
2. Got to webpage where you have to scroll (e.g. macupdate.com or macrumors.com)
3. Scroll to the end

What is the expected result?
No overscrolling or scrolling with rubber band effect, because with an USB cable mouse attached this effect is deactivated system wide under Mac OS X (here: 10.11.5)


What happens instead of that?
Scrolling with rubber band effect.



Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36



 
Components: Blink>Scroll
I've attached a gif of the behavior with a mouse plugged in. This doesn't quite capture the jerkiness of the experience, but it does capture the bounce that should NOT be occurring with a mouse plugged in.
bounce.gif
6.7 MB View Download
Cc: dtapu...@chromium.org
Labels: Hotlist-Input-Dev
I believe this might be related to issue 610841 which interpreted devices with high precision as having phase information which enabled the gesture scrolling.

I cannot reproduce it myself with an Apple A1152 mouse.

Can you please try the Canary build and let me know if it reproduces there?
Labels: Needs-Feedback
The latest Canary build doesn't reproduce it. In the latest official Chrome build 51.0.2704.79 it is still there (also with a A1152).
Mergedinto: 610841
Status: Duplicate (was: Unconfirmed)
The fix for 610841 is also in 52. Since this isn't a security issue it won't be merged into 51; so it would be fixed in the next release train which is 52 itself.

Sign in to add a comment