Anyone for the compose team use autofill? Any chance we can get this merged? <https://android-revie...

# compose

[Colton Idle]

Anyone for the compose team use autofill? Any chance we can get this merged?

https://android-review.googlesource.com/c/platform/frameworks/support/+/1984831

[romainguy]

The team has replied to the PR

[Colton Idle]

ah sorry didn't see that. @tad do you know if you ever got compose + 1password working?

I'm trying to help move the ball forward on either the compose team OR the 1password team to help make compose + 1pass work nicely together.

this was my thread i started with 1pass
https://1password.community/discussion/comment/662612#Comment_662612

[tad]

No I did not, and 1Password 8 no longer works with email fields (in addition to password fields)

[tad]

Additional metadata needs to be supplied via the virtual view hierarchy. I started hacking this into Semantics properties, but hooking it up to AndroidComposeView with onProvideAutofillVirtualStructure is difficult.

[tad]

On the 1Password side, they could be less choosy about what metadata is required in the virtual view. The other autofill services I've tried work fine (Google and Android-Password-Store)

[tad]

There's even a great heuristics library they could use: https://github.com/android-password-store/Android-Password-Store/tree/develop/autofill-parser

[Colton Idle]

damn okay. so it looks like its just dead in the water for now.
as a compose dev and 1pass user... this sucks. lol