Logitech mouse scrolling stop working only in Chrome after a while
Reported by
jay...@gmail.com,
Jan 21 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. connect MX Master mouse (or other Logitech mouse that has "Hyper-Fast Scrolling") and turn on smooth scrolling in Logitech Options 2. Use Chrome for a few days without reboot What is the expected behavior? Scrolling works. What went wrong? Every once in awhile, scrolling will suddenly stop working in Chrome, but scrolling in anywhere else still works. An interesting observation is that if I have something else in front of a Chrome window, and I put the cursor in Chrome, scrolling will work, if Chrome window has the focus, scrolling won't work. A reboot will fix the problem for a few days. Turning off smooth scrolling in Logitech Options also fix the problem, but I don't want to turn that off. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 This might be a Logitech driver or even a Windows 10 bug, but it only affect Chrome, so I'm not sure what's the real cause.
,
Jan 24 2017
,
Mar 15 2017
Here's an update on this, I recently updated to Chrome 57 and the issue still exist, but it will only affect a single tab when it happens (instead of entire Chrome like before), closing that tab and open the same url in a new tab solves the issue.
,
Apr 1 2017
Same problem, MX Master, Windows 10 Insider Preview and 58.0.3029.41 beta (64-bit). It happens on some tabs, but when you change page scrolling comes back. Seems to be random, at least I cannot find any pattern.
,
Apr 3 2017
,
Feb 13 2018
We fixed some issues in Chrome Canary (with some window z-ordering). Are you able to try that version out and let us know if this still exists?
,
Feb 20 2018
This happened to me again today on Stable so I switched to Canary before reboot, but scrolling still doesn't work. The Canary version is 66.0.3350.0 (Official Build) canary (64-bit)
,
Feb 20 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 1 2018
When this happens that the chrome window/tab isn't scrolling while focused, could you please capture and attach a short trace using the instructions here: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug. A short trace while you're trying but failing to scroll over the window should suffice.
,
Mar 8 2018
jayxon@ still waiting on a trace.
,
Mar 8 2018
This haven't happened to me in a while because I kept restarting my computer for other reasons, I'll capture a trace next time it happens.
,
Mar 8 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2018
We have fixed a lot of issues around that code since then and hopefully this issue doesn't happen anymore for you. I'll close this for now but if it ever happened again please feel free to attach the trace to this bug or a new one and we dig into it again.
,
Mar 23 2018
Happened to me again today with 67.0.3379.0 (Official Build) canary (64-bit), trace attached.
,
Mar 26 2018
Thanks for providing the trace. Just to confirm, you were using the wheel over the chrome window while the trace was being captured, right? I'm not seeing any windows events being pumped other than MouseMove so Chrome isn't receiving the mouse wheels from the OS. I'm not sure this is a Chrome bug but putting it in the UI component, maybe someone more familiar with Windows might have ideas on how to further diagnose.
,
Mar 26 2018
Thanks for looking into it. Yes, I am using the wheel in Chrome during the trace. I guess this is probably a logitech mouse driver issue then, however it's weird that it only affect Chrome, but that explains the fact that I have to reboot Windows instead of just Chrome to fix this issue.
,
Nov 21
*** UI Mass Triage *** Closing, since there is no updates since the past few weeks. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by brajkumar@chromium.org
, Jan 23 2017