Add tap-to-scroll to the scroll bars #5349
Conversation
dweymouth
changed the title
There was a problem hiding this comment.
Thanks. I just tested this some more and the behaviour is not quite what I would expect. Should the scroller not go to where I ave clicked? Look at this page in the browser and you should see that clicking on the scroller moves the middle of the scroller to where it was clicked. This does not happen if you for example go to fyne_demo and the Collections -> List page.
|
I based it on what Firefox does. I checked with this page https://worlds-highest-website.com/ - when you tap below the scroll bar, no matter how far down, it barely moves the bar because the page is so long. I just tested with Chromium too and it does the same thing. Edit: and same with Safari too Edit2: Also with long Wikipedia articles where you can see where the text ends up led me to conclude that the behavior is to scroll almost a full pane, regardless of where clicked |
|
This is how Firefox behaves on my end. It seems much more intuitive in my opinion to move to where I clicked rather than just some set of pages at a time: |
|
Oh no.. I guess it may be platform-specific. In which case we probably want to do the same, since we try to fit in with platform conventions. Will test browser behavior on my Linux system too, and Windows VM, but I feel like as a MacOS user, I'm already subconsciously expecting the scroll behavior I implemented here. |
And I expect the opposite 🙈 |
|
Oh, it's a MacOS system setting. Yeah, we should probably try to respect that and read it from the ObjC API, and implement your suggested behavior for all other platforms: https://www.reddit.com/r/Windows10/comments/kjxz1v/scrollbar_jump_to_position_setting/ |
Description:
Tapping above, below, left, or right of a scroll bar will scroll the content up, down, left, or right by a (nearly) full page, respectively. When the scroll bar is large, a new background rectangle is drawn behind it to indicate the taps will go to the scroller and not the underlying content.
Fixes #4922
out.mp4
Checklist: