SUMMARY It would be my expectation that the new navigation mode across virtual desktops, using 3 fingers scrolling gestures, would follow the user-defined scrolling direction. STEPS TO REPRODUCE 1. My preferred scrolling direction is set (in systemsettings/input devices/touchpad/scrolling) to "non-inverted" (i.e. a two-finger scroll-down makes the items lower down visible. OBSERVED RESULT When I use the 3 fingers scrolling gesture introduced in 5.25, the scrolling direction is opposite to the one set (i.e. a three-fingers scroll-down makes the desktop on the top visible) EXPECTED RESULT I would expect scrolling direction to be consistent and to follow the one set by the user. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 (available in About System) KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -
Not sure that makes sense as this isn't a scroll action. It's a swipe action, and those don't generally follow the touchpad scrolling preference.
Hi Nate, thanks for the swift triaging of this item! Would you be so kind as to consider re-opening this bug? I get that from an implementer's perspective it does matter whether something is "scrolled" as opposed to "swiped", but for an "average user" I doubt there is does (in fact, it should probably a feature goal to blur the lines and make them both behave as closely as possible). In my opinion, having the swipe gesture respect the user-defined preference for scrolling direction maximizes satisfaction (by not picking a side in the "natural" vs "traditional" ways) and expectation (of a consistent experience between 2/3 fingers). In any case, thanks for the hard work!
Thanks for explaining it to me that way. That makes sense.
I agree that swipe direction when changing desktop should be configurable. Gesture configurability is on the way and doing this will be very simple and idiomatic when it does. Until then, making it align with scroll direction could be a good stepping stone, but I'm going to stay focused on gesture configurability. I would expect this feature in 5.26 or 5.27.