Repository navigation
Vertical dragging to select text #28676
Description
This PR adds support for text selection by dragging with a mouse. The current implementation only supports horizontal dragging since vertical dragging will most likely conflict with scrolling.
The solution is to make it so that scrolling is only triggered when initiated by touch events, and vertical text selection is only triggered by a mouse. No conflicts!
But with the current state of Flutter, we can't disable mouse-drag-to-scroll yet because there is no other way to scroll on desktop. Once wheel scrolling is fully implemented, we can revisit this.
- wheel scroll.
- scroll bars.
- disable drag-to-scroll when the device is a mouse.
- enable text selection by dragging in any direction.
Activity
stuartmorgan-g commentedon Aug 13, 2019
Is there work remaining here?
xxgreg commentedon Dec 14, 2019
I've run into a similar issue where I'd like to handle a vertical drag, but this isn't possible inside a Scrollable widget as far as I can tell.
One possible solution is to add an option to Scrollable to disable tap&drag scrolling. Two-finger trackpad and mouse-wheel scrolling would continue to work when this is set.
My current use case is desktop only. But there's probably a more general solution here, which would set the Scrollable option automatically based on the current platform.
timsneath commentedon Jan 2, 2020
Pinging @mdebbar to check whether this issue is still relevant?
mdebbar commentedon Jan 2, 2020
@timsneath I added checkboxes in the issue description to clarify which parts are done and which ones are still missing.
timsneath commentedon Jan 3, 2020
Great - thanks!
mdebbar commentedon Dec 7, 2020
The only piece of work left here is tracked in: #71322
kevlar700 commentedon Mar 5, 2021
I believe that this isn't quite complete. Selecting text and dragging above the screen should cause scrolling and more selection?
Shouldn't arrow keys and page down/up also work by default?
github-actions commentedon Aug 3, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.