Bug P2
Status Update
Comments
ch...@gmail.com <ch...@gmail.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
ae...@google.com <ae...@google.com> #3
I found an example
D/Autofill Status: Autofill popup isn't shown because autofill is not available.
Did you set up autofill?
1. Go to Settings > System > Languages&input > Advanced > Autofill Service
2. Pick a service
Did you add an account?
1. Go to Settings > System > Languages&input > Advanced
2. Click on the settings icon next to the Autofill Service
3. Add your account
Is this a bug on your side or do the app developers of these password managers need to change their implementation?
ap...@google.com <ap...@google.com> #5
deleted
ma...@gmail.com <ma...@gmail.com> #6
Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.
Description
I'm currently writing a custom
FlingBehavior
which handles flings from the Lazy layouts. Unfortunately I'm seeing weirdness in the velocity values provided.It seems that if you perform a number of flings in alternating directions (left then right, repeat), the velocities accumulate.
I had a quick look through draggable, and I'm not seeing anywhere where the VelocityTracker is being reset. I'd expect a call tohttps://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/Draggable.kt;l=329
velocityTracker.resetTracking()
somewhere around here:Is this intentional?