Fixed
Status Update
Comments
kl...@google.com <kl...@google.com>
kl...@google.com <kl...@google.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
an...@google.com <an...@google.com>
va...@google.com <va...@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?
va...@google.com <va...@google.com> #5
deleted
Description
Currently
AndroidComposeView
reads a system property to determine whether the developer option "Show layout bounds" has been enabled, and if so, every layout node draws its bounds. But we only read that value from the system when the lifecycle hosing the ACV is resumed. When the setting is changed from a quick settings tile, the activity is never paused, so it won't pick up the new setting. Android Views behave as expected: When the quick setting tile is toggled, they immediately start drawing their bounds. Compose should do the same.There is an API for registering for property changes that we might be able to use:https://cs.android.com/android/platform/superproject/+/master:frameworks/base/core/java/android/os/SystemProperties.java;l=244;drc=fcdba12869220502f025217077317251155d152f