StatusDraggableListItem: drag by handler on mobile by default #19096
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dragByHandler property made true by default on mobile to avoid events interception resulting with no ability to scroll by flick Closes: #19060
Jenkins Builds
|
caybro
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the PR do
dragByHandlerproperty made true by default on mobile to avoid events interception resulting with no ability to scroll by flickEffectively it fixes scrolling by flick on mobile in various places:
Closes: #19060
Affected areas
StatusDraggableListItemArchitecture compliance
My PR is consistent with this document: QML Architecture Guidelines
Screencapture of the functionality
Record_2025-10-21-01-28-17.mp4
Record_2025-10-21-01-34-18.mp4