User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 Steps to reproduce: When scrolling by holding down the scroll wheel and moving the mouse up and down the scroll eventually cuts out and the page stops scrolling. Sometimes this may take a while to occur and I am not sure if it happens on any given page. I am not always able to reproduce the behaviour exactly. I do not recall this issue happening in Firefox prior to 52.0. I also tested against other browsers to verify that this wasn't a hardware issue with my mouse. Actual results: I tried scrolling by holding down the scroll wheel and moving my mouse which causes the scroll to eventually cut out. Expected results: The page should keep scrolling until I release the scroll wheel.
Also forgot to mention but I made sure that the mouse stays within the scroll area so this does not appear to be a case of: https://bugzilla.mozilla.org/show_bug.cgi?id=260119
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 I have tested this issue on Windows 10 x64 with Firefox release (51.0), the latest Firefox release (52.0) and the latest Nightly (55.0a1-20170314030215) and haven't managed to reproduce it. After navigating to different websites (eg: twitter.com, cnn.com, youtube.com, etc), when scrolling by holding down the scroll wheel and moving the mouse up and down, the scroll works as expected. Can you please retest this using a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/AR5o9d).
I tested with both a new profile and in safe mode and was able to reproduce the issue both times. I will try to provide a bit more information. Sometimes the scroll issue can take a while to occur. Here is a page I tested on where I could consistently reproduce the issue: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=scroll&list_id=13493089 Steps to reproduce: 1. Hold down scroll wheel and move mouse vertically to scroll. 2. Scroll to top of page then bottom, then top, etc. without ever letting go of the wheel. 3. Repeat this process until the scrolling cuts out. Sometimes it will cut out quickly, sometimes only after scrolling up and down a number of times (ex. 5+). I've noticed that it seems somewhat more likely to cut out when the scrollbar has reached the top of the page although this doesn't always happen.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 I have re-tested this issue on Windows 10 x64 with Firefox (52.0), the latest Firefox release (52.0.2) and the latest Nightly (55.0a1-20170328095415) and haven't managed to reproduce it. After following the STR described in comment 3, while holding down the scroll wheel and moving the mouse up and down, several times, I have only observed some scattering, but haven't managed to cut out, whenever reaching the top, bottom or middle of the page. I'm not entirely sure what are you referring to "cut out", you continue to hold the middle click down, move up/down and the scrolling stops? Taking in consideration that you mentioned that this didn't happen in Firefox prior to 52.0, this seems like a regression. If you have time, can you please use the mozregression tool in order to find the bug that has introduced this issue. You can find the tool here: http://mozilla.github.io/mozregression/install.html#mozregression I recommend the command line tool, fairly simple to use, after installing just run the following code: "mozregression --good 51 --bad 52" and you can check the builds in order to find the issue. * Considering that you can't reproduce the issue in 51. Thank you.
> I'm not entirely sure what are you referring to "cut out", you continue to hold the middle click down, move up/down and the scrolling stops? Yes. The scroll indicator (this: https://i.imgur.com/C3XKfJW.png) disappears and the page abruptly stops scrolling despite that I have taken no steps to stop scrolling. I will try running that regression tool when I have time. I am not 100% sure that this behaviour doesn't occur in 51 but I don't recall experiencing the issue until updating to 52. I might try testing out 51 first just to verify that I can't reproduce it there.
Hi, have you managed to re-test this on FF 51? Did you managed to find the time to perform a regression as specified in comment 4? Thank you.
According to the details mentioned the problem cannot be reproduced FF52 and 1 prior version. Regression tool running also has displayed no error in this matter.
I have not yet tested FF51. I will try out 53.0 first when it releases to see if I can still reproduce it there and then if so I will test older versions. PS: Is there a way to install older versions of Firefox without it affecting my current install?
For testing older versions of Firefox without affecting your current profile, you can use the mozregression tool from here: http://mozilla.github.io/mozregression/install.html It's fairly simple to use, you can download any version of Firefox by date, simply writing the following command lines(after installing mozregression): - to find the bug that introduced the regression: mozregression --good 2015-12-25 --bad 2017-05-03 - to simply check if the issue is reproducible on one of the specific builds: mozregression --launch 2016-05-05 Find out more about this here: http://mozilla.github.io/mozregression/quickstart.html Also if you'll like to learn more about Firefox profile manager here is where you can look into: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles I do suggest trying using the mozregression tool and find the regression if there is. Thank you.
Marking this as Resolved - Incomplete due to the lack of response from the reporter. If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
Sorry for the lack of response, this issue largely went away in later versions of Firefox and I somewhat forgot about the report. I just tested it out again and I am no longer able to reproduce the problem in 55.0.1.
You need to log in before you can comment on or make changes to this bug.