In an account large enough to need scrolling, when I scroll with the mouse by pressing the left mouse button over the thumb and moving the mouse up and down (but also a bit left and right unintentionally), the scrolling stops as soon as the mouse pointer re-enters the scrollbar. In short, to reproduce the bug: 1. Open an account large enough to need scrolling. 2. Press and hold the mouse button over the thumb of the scrollbar. 3. Move the mouse up-left: this will scroll upward, and the mouse pointer will leave the scrollbar to enter the work area of the window. 4. Move the mouse up-right or down-right: this will scroll upward or downward, but only until the mouse pointer re-enters the scrollbar. The bug also occurs when inverting left and right (i.e. with the mouse pointer leaving the window and re-entering). Note: When I start scrolling, the thumb changes from gray to dark blue. When scrolling stops due to this bug, the thumb changes back to gray, as if I had released the mouse button.
Does this happen with a report too? What distro & version?
I've tried several reports, and the bug does not occur there. It does not occur either in the list of the accounts. Debian/unstable (package gnucash 1:3.10-1). In case this matters, I use the fvwm window manager, no desktop environment.
OK, it's a register problem rather than a Gtk one. Thanks.
Same problem as https://bugs.gnucash.org/show_bug.cgi?id=797755 : After scrolling, slider and register contents snap back ?
No, it is not the same problem. In my case, the scrolling just stops, as if I released the mouse button. Nothing snaps back.
This I think is down to gnucash_register_enter_scrollbar in gnucash-register.c which was used from the start of the 3.x series to fix a potential bug in gtk+3.20 which still seems to be open. https://bugzilla.gnome.org/show_bug.cgi?id=765410 https://gitlab.gnome.org/GNOME/gtk/issues/615 Will try and remove it and see if it works ok.
I have removed this old fix and tried in Windows 10 and a couple of flavours of Linux and I am unable to reproduce the old problem so have pushed this to master and so will be fixed for version 4.0
