New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS 13] Long press and drag to select #35010
Comments
|
Tapping and dragging without waiting for a long press still drags the cursor around. |
|
Seems like the same behavior as Android on #26394 now. |
|
@DanielEdrisian here's another one you could give a try. It's slightly more involved than the last one but should still be somewhat straightforward. We already have some infrastructure to handle various combinations of gestures in textfields. #26001 has some example of the current behavior of long-press-dragging translating to moving a collapsed cursor. It seems like the new behavior is to select the current word and then expand the selection by letters. Part of the plumbing goes through
onSingleLongTapMoveUpdate.
You can get some ideas for possible options such as
|
|
I just double checked quickly but it seems unfortunately like the premise of the bug isn't correct anymore on the latest iOS version It seems like the default iOS behavior was closer to our current implementation now (though the long-press-drag now shows the cursor not bound to the textfield itself like the keyboard force-touch-press-drag magnifier). Did I hold it right? |
|
@xster I believe when the text isn't focused, long press and drag does text selection. Once it has focus it only selects a range in double tap drag. |
|
Spoke offline. @DanielEdrisian is correct, it's different when focused vs non-focused. |


In iOS 13, long pressing on editable and non-editable text starts selecting. Dragging extends the selection. I think this is identical to Android now, so it should be easy for Flutter to support. Previously, long pressing and dragging on text set the cursor and showed the loupe magnifying glass.
This was shown at WWDC in this video around the 30:00 mark. I also confirmed this in the iOS 13 simulator.
The text was updated successfully, but these errors were encountered: