Address update dialog is hard to interpret [400343419]

Project

Status Update

No update yet.

Description

ba...@google.com

created issue #1

Mar 3, 2025 08:44AM

I was recently presented the attached screenshot.

Note how the difference between the old and the new address is just a comma between the street name and the house number.

In the old (incorrect) state the address was:
Address line 1: Street
Address line 2: House number

The new (correct) state the address became:
Address line 1: Street House number

I don't think that users would understand this.

I would propose that we render the address lines as separate rows.

Update address.png

22 KB

View

Download

Comments

ba...@google.com <ba...@google.com> #2Mar 3, 2025 08:45AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <radhanakade@google.com>
Link: https://android-review.googlesource.com/3510337

Migrate traffic from pixel2 to mediumphone on FTL emulators.

Expand for full commit details

Migrate traffic from pixel2 to mediumphone on FTL emulators. 
 
Bug: 396715333 
 
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33 
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2

Files:

M buildSrc/private/src/main/kotlin/androidx/build/FtlRunner.kt

Hash: c76f8094154101867327912e659ae47509755957
Date: Wed Feb 26 11:27:46 2025

sk...@google.com <sk...@google.com> #3Mar 3, 2025 09:06AM

Assigned to sk...@google.com.

thank you for filing this bug, dominic. i agree from a UX point of view. i've actually just started looking into our update prompts, and discussed with other stakeholders how we may improve them in the future. we should coordinate next steps for general updates.

ba...@google.com <ba...@google.com> #4Mar 3, 2025 11:40AM

Just double checking: do you want to block work on this to coordinate on general updates or would it make sense to land a (hopefully small) fix? I am always a bit concerned of perfect being the enemy of the good.

sa...@google.com <sa...@google.com> #5Mar 3, 2025 02:24PM

I view this as a bug with a (hopefully small) fix.

Dominic, what's the best metric we can measure the improvement we're trying to see here (i.e. false positive update prompts)?

sk...@google.com <sk...@google.com> #6Mar 3, 2025 02:33PM

with regards to your comment 4 dominic: i'm not opposed to this short-term fix, as it feels more like a bug fix, than a change in layout. let me know if you need anything from my side.

ba...@google.com <ba...@google.com> #7Mar 3, 2025 02:41PM

Status: New

#5: Ali: Autofill.ProfileImport.NewProfileDecision2.Aggregate should grow in acceptance.

#6: thanks, stephan. i will un-assign the bug from you so that an engineer can pick it up. shall i create a copy of the bug for the longer-term questions that I assign to you?

sk...@google.com <sk...@google.com> #8Mar 3, 2025 02:44PM

yes please, thank you dominic

sy...@google.com <sy...@google.com> #9Mar 3, 2025 04:30PM

Comment has been deleted.

Message last modified on Mar 3, 2025 04:32PM

sy...@google.com <sy...@google.com> #10Mar 3, 2025 04:51PM

I cannot reproduce this, things I've tried (using German profile as I assume that's what was used):

Profile that was saved with al1 "street_name" and al2 "15" and then both filled into al1
Profile that was saved with al1 "street_name" and al2 "15" and then filled filled into street name and house humber fields
Profile that was saved from street name and house number fields and then filled into al1

The only repro steps I could find, was to create a profile with "Street 15" as a street name and then submit a form with "Street, 15" street name, but I believe that is WAI

IssueTracker

This issue is a part of the Chromium tracker.