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

Issue 669574 link

Starred by 1 user

Issue metadata

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


Show other hotlists

Hotlists containing this issue:
Fixing-touch


Sign in to add a comment

Some mouse scroll directions affected by touchpad settings.

Project Member Reported by hcameron@google.com, Nov 29 2016

Issue description

Chrome Version: 54.0.2840.101 (64-bit)
Chrome OS Version: 8743.85.0 (Official Build) stable-channel samus
Chrome OS Platform: Chromebook Pixel 2015 LS
Network info: N/A

Steps To Reproduce:
(1) Have "Australian scrolling" enabled in touchpad settings
(2) Connect Corsair M65 Pro mouse
(3) Use scroll wheel

Expected Result:

Content scrolls up and down as normal.

Actual Result:

Content scrolls in opposite direction to expected. Only this specific mouse is affected; other mice connected at the same time scroll correctly. If the touchpad settings are changed to "Traditional scrolling", the mouse will scroll correctly.
 
Cc: kathrelk...@chromium.org
Components: UI>Input>Touch Blink>Scroll IO>Mouse
Labels: M-54
Summary: [Samus] Mouse scroll direction affected by touchpad settings. (was: Mouse scroll direction affected by touchpad settings.)
Cc: spang@chromium.org
Owner: asimjour@chromium.org
Interesting, I think that setting should only affect multi-touch scrolling (touchpad, touchscreen).

asimjour@: any ideas? or do you know who would be the right person to look at this?

Comment 3 by hcameron@google.com, Feb 16 2017

FWIW, this also seems to happen with a Logitech MX Master mouse.
Cc: asimjour@chromium.org
Owner: adlr@chromium.org
Labels: -Pri-3 Pri-2
Status: Assigned (was: Unconfirmed)
If mice are broken this should be higher than pri-3
Summary: Some mouse scroll directions affected by touchpad settings. (was: [Samus] Mouse scroll direction affected by touchpad settings.)
Can repro with the Logitech MX Master but not several other mice.  Not specific to Samus.  See also  issue 351560 
Any updates on this?
This seems to be fixed now; presumably as part of https://bugs.chromium.org/p/chromium/issues/detail?id=351560

Sign in to add a comment