scrolling in single-page-view continues endlessly beyond invisibility of content
Reported version
3.6
Type
Ergonomical (UX)
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Any score in single-page view: Scroll up or down by mouse wheel and continue moving the wheel for a while after content moves out of visibility --> The movement can continue endlessly beyond visibility. After this, scrolling back in unlimited length is necessary. This can become a trap (loosing any sight and not regaining).
Comments
Relates to #275844: [EPIC] Single page view related issues
Confirmed, this is true even when using the preference to constrain scrolling to page borders.
In reply to Confirmed, this is true even… by Marc Sabatella
When repairing, please take care to allow a certain tolerance, so that the edge of score can go out at least until the middle of the window, or more. Otherwise, when strongly zooming out (zooming small, by wheel + Ctrl), the limit could cause unwanted scrolling, losing the spot when zooming-in again. Scrolling should remain fully reversable, as it is now.
RIght, this was a consideration when implementing the constrain option mentioned above and why it isn't enabled by default.
BTW, depending on where you'd like to return to, there are keyboard shortcuts to get you there. Eg, Home to take you to the first measure, End to the last, or Shift+L to restore your previously selected location.
In reply to RIght, this was a… by Marc Sabatella
Thank you! These are helpful hints.
About scroll-limit, certainly a solution exists which prevents from endless scrolling but not interferes when zooming. Zoom-out can never bring the position as far out as scroling does now.
... you say: Shift+L to restore your previously selected location.
Is that correct? It does not work on my computer.
In reply to ... you say: Shift+L to… by Steve3
... sorry, I take it back. It works, just only after scrolling, not after going to another spot. Thank you!
It always works to re-establish the selection, and if necessary, to reposition the view there. If the selection is already in view, there is nothing to do. Except, it will force a screen reader to re-read the information about the selection, which is actually the reason the command was implemented.
Came up again in https://musescore.org/en/node/321426