Status Update
Comments
sh...@google.com <sh...@google.com> #2
We could add an API to make the weighted distance customizable, aosp/3271691 has more info.
ae...@google.com <ae...@google.com> #3
Reassigning to qqd@ as a default since Shep is no longer on the team.
si...@google.com <si...@google.com> #4
I checked on Android Views and Chrome Android.
- Double click, triple click does not work on regular ~Text
- Double click, triple click does work on ~TextField
si...@google.com <si...@google.com>
ob...@gmail.com <ob...@gmail.com> #5
[Deleted User] <[Deleted User]> #6
si...@google.com <si...@google.com> #7
Grant, I assigned this to you since you are working on this (or some part of it) already.
Please feel free to dup to another ticket that is under your radar. (or if I am mistaken assign back to team alias)
sh...@gmail.com <sh...@gmail.com> #9
I want to add another one bug:
Clicking on the selection "handle" in android views opens ActionMode context menu, nothing happens in compose views.
Should you fix that too?
gr...@google.com <gr...@google.com> #10
Are you thinking of
sh...@gmail.com <sh...@gmail.com> #11
Will this issue (with double tap) added to a new build version?
gr...@google.com <gr...@google.com> #12
double and triple tap are on our radar, but likely won't be implemented soon. Double and triple click (from a mouse) is coming soon, but the touchscreen version (double/triple tap then drag) is not planned right now.
ja...@gmail.com <ja...@gmail.com> #13
as...@gmail.com <as...@gmail.com> #14
gr...@google.com <gr...@google.com> #15
Updated the description with the current status of this FR by component.
cs...@google.com <cs...@google.com> #16
mi...@gmail.com <mi...@gmail.com> #17
Isn't this something important to be part of the functionality of a TextField?
st...@gmail.com <st...@gmail.com> #18
BasicTextField2 is gone in 1.7.0 and 'double tap to select' is not working again no matter which overload I use
Upd. okay, my bad, selection works with the state: TextFieldState
overload, but not with the other two. The gestures, however, are still not "native". Double tap to select only works if the cursor position hasn't changed within a single word. This is different from EditText and other View system input views where it'll select a word regardless of the previous cursor position.
gr...@google.com <gr...@google.com> #19
The gestures, however, are still not "native". Double tap to select only works if the cursor position hasn't changed within a single word. This is different from EditText and other View system input views where it'll select a word regardless of the previous cursor position.
Can you be more specific? The cursor position doesn't seem to be affecting selection starting on BTF2 double tap.
st...@gmail.com <st...@gmail.com> #20
Can you be more specific?
Sure, see attached video. Using androidx.compose.material3:material3:1.3.0-beta05
and androidx.compose.foundation:foundation:1.7.0-beta07
gr...@google.com <gr...@google.com> #21
Can you turn on pointer taps in the future when recording? I can't tell if there are any taps that don't have any effect.
I think the only thing you are pointing out is that the second tap of a double tap can be anywhere on the word in EditText, correct? The logic right now in Compose requires the double tap to be within touchSlop of each other.
Anything else in the video that I'm missing from extra taps?
st...@gmail.com <st...@gmail.com> #22
I'm sorry for that poor emulator recording. Regarding your second paragraph - yes, correct, this is exactly the issue we'd like to get a fix for
Description
Features:
Components with selection gestures:
SelectionContainer
-BasicText
s within aSelectionContainer
.BasicTextField
overloads withvalue: TextFieldValue
andonValueChange
.BasicTextField
overloads withstate: TextFieldState
.Current double-tap support:
Current triple-tap support: