Bug 458097

Summary:	GlobalDrawer is not scrollable by flicking
Product:	[Frameworks and Libraries] frameworks-kirigami	Reporter:	Rinigus <rinigus.git>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	nate, notmart
Priority:	NOR
Version First Reported In:	5.97.0
Target Milestone:	Not decided
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rinigus 2022-08-20 12:27:32 UTC

SUMMARY
***

On mobile environment, I cannot scroll items in GlobalDrawer by flicking

STEPS TO REPRODUCE
1. Install Kirigami Gallery from flatpak kdeapps 
2. QT_QUICK_CONTROLS_MOBILE=true flatpak run org.kde.kirigami2.gallery
3. Open GlobalDrawer on the left
4. Reduce height of the window to have some items in the drawer hidden

OBSERVED RESULT

Observe that you can scroll using mouse wheel but not by holding some location (left mouse button pressed down) and flicking the drawer. Even the scrollbar on the drawer is not selectable by mouse

EXPECTED RESULT

I can flick the drawer up and down to choose hidden menu items

SOFTWARE/OS VERSIONS

KDE Application Platform  org.kde.Platform                                    5.15-21.08 flathub
Kirigami Gallery          org.kde.kirigami2.gallery                           master     kdeapps

Sat 20 Aug 2022

Comment 1 Rinigus 2022-08-20 12:33:26 UTC

Looks like running with 

QT_QUICK_CONTROLS_MOBILE=true QT_QUICK_CONTROLS_STYLE=Plasma flatpak run org.kde.kirigami2.gallery

makes scroll bar selectable by mouse. But it is still impossible to flick.

Comment 2 Nate Graham 2022-08-23 13:02:48 UTC

This is actually intentional: when you use the mouse, you're not flicking at all, you're clicking and dragging. Clicking and dragging is different from flicking with a finger, and we have gotten bug reports about clicking and dragging performing a scroll unexpectedly. I can confirm that flicking with an actual finger on an actual touchscreen works here. So technically the issue you're seeing was a bugfix. :)

Comment 3 Nate Graham 2022-08-23 13:03:29 UTC

*** Bug 458131 has been marked as a duplicate of this bug. ***

Comment 4 Rinigus 2022-08-23 17:00:51 UTC

OK, fair enough. I was not aware (or didn't recall to be more precise) of it. Thanks for looking into it.