Use unclipped bounds when asserting or printing node positions [161336532]

Fixed

Bug

Status Update

No update yet.

Description

je...@google.com

created issue #1

Jul 15, 2020 11:00AM

When asserting the position of a node, or when printing positions of nodes in the semantics tree, use the unclipped bounds instead of the clipped bounds. Using the clipped bounds is confusing to the user, and makes it impossible to distinguish between a correctly sized node that is clipped to size S, and an incorrectly sized node that is clipped to size S.

Comments

je...@google.com <je...@google.com> Jul 17, 2020 02:46PM

Accepted by je...@google.com.

ap...@google.com <ap...@google.com> #2Jul 21, 2020 12:35PM

Marked as fixed.

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

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

ap...@google.com <ap...@google.com> #3Jul 28, 2020 01:11PM

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?

Issue 161336532

Description

Issue summary

Comments

je...@google.com <je...@google.com> Jul 17, 2020 02:46PM

ap...@google.com <ap...@google.com> #2Jul 21, 2020 12:35PM

ap...@google.com <ap...@google.com> #3Jul 28, 2020 01:11PM

Add comment

Issue metadata