New issue
Advanced search Search tips

Issue 836159 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Wrong first name and last name is displaying under ‘Credit card’ section in walmart.com

Reported by dchau...@etouch.net, Apr 24 2018

Issue description

Chrome Version: 67.0.3396.18(Official Build)Revision 399b73768e46f9219d4868a2ad1ccb517da5347d-refs/branch-heads/3396@{#251} 32/64-bit.
OS: Win(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.5) and Linux (14.04 LTS).

What steps will reproduce the problem?
1. Launch Chrome and navigate to chrome://settings/autofill 
2. Fill all the details under ‘Addresses’ and ‘Credit cards’ section and make sure the name of ‘Addresses’ and ‘Credit Cart’ should be different.
3. Go to https://www.walmart.com/, Add any item to cart, proceed to checkout and enter the shipping address using auto-filled data and continue.
4. Now go to ‘Enter payment method’ section and observe ‘First name on card’ and ‘Last name on card’ under the ‘Card information’ fields.

Actual: ‘Card information’ fields takes First name and last name of ‘Addresses’ section auto-filled data instead of ‘Credit card’ section. 
Expected: ‘Card information’ fields should takes auto-filled data from ‘Credit Cards’ section(‘Name on card’ on “Edit card” overlay).

This is a non-regression issue, seen from M-60 series.

NOTE: This issue is also reproducible on M-66 Stable & Beta (build # 66.0.3359.117) and M-68 Canary (build # 68.0.3405.0).

Kindly review the attached screen-cast for reference.

 
Actual_behavior.mp4
2.1 MB View Download
Status: Untriaged (was: Unconfirmed)
As this being a Non-Regression issue, changing the status to Untriaged so that the issue would get addressed.

Thank You!

Comment 2 by se...@chromium.org, May 1 2018

Owner: rogerm@chromium.org
Status: Assigned (was: Untriaged)
The site developer has used the autocomplete attribute for given name and last name instead of credit-card related name fields.

Both the field prediction heuristics and the server predict the fields as credit card names, but we're deferring to the site dev.

This might be something we can "rationalize"? Promoted the final type to CC-name based on the absence of other non-CC related fields and the presence of other CC related fields.

Sign in to add a comment