GNOME Bugzilla – Bug 773618
Enable scrolling more quickly or precisely
Last modified: 2018-05-02 17:42:19 UTC
On using scrollbars I'm noticing that they are not utilizing their full potential if they have to handle large documents and maybe this can be enhanced: - I'm noticing that there is a minor scroll acceleration for example if the scrollwheel is moved fast (not sure if this comes from SciTE or GTK+). If missing this feature could be implemented directly and in either case I think it should be more aggressive at default. - Scrolling on the scrollbar (hovering the mouse over it and using the scrollwheel) acts like the above except that larger steps for scrolling are used but this is still not enough on large documents. In case this is a SciTE-specific feature it could be implemented directly too and in either case the accelerating here should maybe switch to percent based scrolling (like 1% steps) on high accelerations to allow a fast but precise scrolling through these documents. - Steppers (if enabled) have no short pause after being clicked before they automatically activate autorepeat. This makes it hard for pixel-perfect scrolling on a click. Also these enhancements could be bind to settings in case users want to justify their behavior.
This is a bit too vague to do much with and probably needs an update for 3.22 too Re your 1st point: When using a touchpad, scrolling fast/far over the content does result in the content moving more quickly in GTK+. Using a mouse, however, this is not the case. Re your 2nd point, I see the opposite: using the mouse wheel over the content is faster than over the scrollbar itself. Besides, "more aggressive" is not really actionable; you would need to attempt to quantify it with an example of a real-world use case. I doubt new settings would get added for these, given past evidence. But for completeness, see https://bugzilla.gnome.org/show_bug.cgi?id=734397 for another.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/695.