I just got a new computer with Windows 10 (I had Windows 7 before this) and when I installed LibreOffice on it I was disappointed to find that inertia scroll on the track pad doesn't work. I've tried both the most recent version (6.1.2) and the one I had on my last computer (220.127.116.11) which was running Windows 7, where it worked fine.
I'm not sure if "inertia scroll" is a commonly used term. What I mean is that now I have to scroll many, many times to get to the top or bottom of my document, where before I could do a few scrolls and then it would just keep coasting.
This feature works fine on other programs on my computer (e.g. with Google Sheets) so I don't believe it's a system specific problem (e.g. drivers).
I need it especially for Calc but I see that it also doesn't work in Writer.
The reason I need it is for when I select a block of cells in Calc that spans many pages, so I can re-sort the rows by different criteria without including my five header rows. I usually select a cell at the bottom corner and then scroll all the way to the top (almost the top, but not the header rows), hold down the shift key, and then select the cell at the diagonally opposite corner of that large block of cells. Since not all the cells are filled, using the <ctrl><shift> and arrow keys is a little less convenient.
Steps to Reproduce:
1.scroll with a trackpad, several times in a row, using a quick flick
The document scrolls down a small chunk for each scroll and comes to a complete stop after each scroll.
The document should have kept coasting for awhile after those few scrolls, so that I can actually go to the end of the document.
User Profile Reset: Yes
OpenGL enabled: Yes
This is a description of coasting that describes what I used to have in LibreOffice and don't have anymore:
There's a certain "momentum" to scrolling that is entirely dependent on how quickly you flick your fingers (or mouse) to scroll; slow scrolling motions have almost no momentum to them at all, while fast flicks mean the screen continues to scroll long after your fingers/mouse have left the tracking surface, possibly even scrolling all the way to the top or bottom of what you're scrolling through in a matter of seconds.
This may not be related but I've also noticed that LibreOffice seems to be slower on my new setup, taking longer to open files.
Correction. Only applies to scrolling with trackpad. Ignore references to mouse.
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker