PxBounds should be Rect [162627058]

Fixed

Bug

Status Update

No update yet.

Description

mo...@google.com

created issue #1

Aug 1, 2020 12:14AM

PxBounds should be removed and Rect should be used everywhere PxBounds is used.

Comments

ap...@google.com <ap...@google.com> #2Aug 5, 2020 12:42AM

Marked as fixed.

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

wa...@gmail.com <wa...@gmail.com> #3Jan 29, 2025 12:06PM

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

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?

jo...@gmail.com <jo...@gmail.com> #4Jan 29, 2025 12:12PM

Comment has been deleted.

Message last modified on Jan 29, 2025 12:15PM

jo...@gmail.com <jo...@gmail.com> #5Jan 29, 2025 12:16PM

Comment has been deleted.

Message last modified on Jan 29, 2025 12:16PM

jo...@gmail.com <jo...@gmail.com> #6Jan 29, 2025 12:21PM

Comment has been deleted.

Message last modified on Jan 29, 2025 12:47PM

jo...@gmail.com <jo...@gmail.com> #7Jan 29, 2025 12:48PM

Hello, I am trying to implement the same thing - it seems like there's no way for current password managers like 1Password or Bitwarden, to automatically pick up the fields. Is there a possible solution?

Issue 162627058

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Aug 5, 2020 12:42AM

wa...@gmail.com <wa...@gmail.com> #3Jan 29, 2025 12:06PM

jo...@gmail.com <jo...@gmail.com> #4Jan 29, 2025 12:12PM

jo...@gmail.com <jo...@gmail.com> #5Jan 29, 2025 12:16PM

jo...@gmail.com <jo...@gmail.com> #6Jan 29, 2025 12:21PM

jo...@gmail.com <jo...@gmail.com> #7Jan 29, 2025 12:48PM

Add comment

Issue metadata