Fixed
Status Update
Comments
je...@google.com <je...@google.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
po...@google.com <po...@google.com>
ad...@google.com <ad...@google.com>
ap...@google.com <ap...@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?
Description
Currently,
Modifier.composed { /*code*/ } != Modifier.composed { /*same code*/ }
, which can lead to unexpected results in some cases.For example,
Modifier.testTag("tag")
is inferred to be static, butModifier.testTag("tag") != Modifier.testTag("tag")
, which will make a difference when Live Literals is enabled.To fix this, we need to implement
ComposedModifier.equals()
, which is not possible because we can't meaningfully compare lambdas with each other. As an alternative, we can add a version ofcomposed
that accepts a key to base equality on.Simplified, something like this: