I’d bind it to up/down scrolling along the left/right edges.
If there’s a pulley, pull it (no list scrolling)
If there’s no pulley, just do the list scrolling (current behaviour )
I think edges are generally underused.
1 Like
This is basically what Aurora OS does.
Sacrificing quick scroll is a really poor solution.
Wasn’t pulley access in long lists the main issue - and here we’d give up a key feature for interacting with long lists?
1 Like
I don’t think it sacrifices anything. The quickscroll doesn’t seem to depend on where the finger touches the screen (edge or centre ).
As far as I can see there is no specific UI role assigned to 'sweeping along the edges '.
To push things further, I’d even like the bottom edge swipe connected to back/next of the native browser (hence no collision with the sweeping in the browser content )
What?!
Sure; the option to qick-scroll activates when scrolling anywhere - but using it most certainly takes using the rightmost part of the screen.
And very well so. Gazillions of actions everywhere is no good. I would bet that would get activated lots of times when you try to do a from-edge swipe.
No arguments from me there - i’d gladly give up from-bottom swipe any day of the week. But this is not the thread for that.
1 Like
Many of the solutions can be indeed solved by a context menu.
However, I have seen it being used many times where it isn’t really supposed to. Like “Mark multiple Emails” or “Search” could be binded to a context menu, but they are not supposed to be there.
Pull menus are supposed to be for “global” actions for the screen in question, context menus are related to the “item row”. Mixing these together is just confusing to the end user.
Different scroll ares for pulley and list seem to me just hacks and precise control, which we should try to avoid. Since Sailfish also has a lot of actions going on towards the edge of the screen, these kinds of additions would make it more likely for errors to appear.
However, maybe a bottom toolbar, which could be used to bring up the pullup menu is the simplest choice (and make it disappear when scrolling / interacting with the element).
Personally, my other favorite way to solve this globally, would be the swipe from the edge + swipe either down or up.