New issue
Advanced search Search tips

Issue 616343 link

Starred by 2 users

Issue metadata

Status: Available
Merged: issue 699530
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug

Blocking:
issue 699530



Sign in to add a comment

Id code field is recognized as username field on chaseonline.chase.com

Project Member Reported by hwi@chromium.org, Jun 1 2016

Issue description

1. When signing into chaseoneline.chase.com on a new computer, there's an additional step asking an id code + password. (screenshot 01)
2. The id code field is autofilled with the username saved previously: incorrect fill (from user perspective). 
3. When the id code + pwd are submitted, on the next screen, the password update prompt is asking to update the username with the id code, which is not desired. (screenshot 02) 
 
02-chase-update-pwd.png
3.2 MB View Download

Comment 1 Deleted

Comment 2 by hwi@chromium.org, Jun 1 2016

01-chase-id-code-autofill-incorrect copy.png
3.7 MB View Download

Comment 3 by vabr@chromium.org, Jun 1 2016

Labels: Hotlist-Polish
Status: Available (was: Untriaged)
Thanks for the report!

I cannot find the exact form appearing on the screenshot in comment #1, but I suppose both fields are part of the same form. If so, then currently there is no way for Chrome to understand that the text field on the left is not a username, unless the webpage author uses the autocomplete attributes to annotate the password field, and a (hidden) dummy username.

Fortunately, this is not a fatal issue, because the user can change the username on filling, but it may look confusing and deter the user from saving.

Potential fixes could involve:
* Try to measure the distance (visual or in HTML code) between the text and password fields: if they are too far apart, we could lower the confidence of what is the username and offer the empty username as an option for saving.
* Messaging better during saving that the saved username can be corrected during filling.

Comment 4 by vabr@chromium.org, Jun 7 2016

Cc: -vabr@chromium.org

Comment 5 by kolos@chromium.org, Mar 8 2017

Mergedinto: 699530
Status: Duplicate (was: Available)

Comment 6 by kolos@chromium.org, May 24 2017

Blocking: 699530
Status: Available (was: Duplicate)
Project Member

Comment 7 by sheriffbot@chromium.org, May 24 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by vabr@chromium.org, Jun 1 2018

Status: Available (was: Untriaged)
Cc: battre@chromium.org
 Issue 770185  has been merged into this issue.

Sign in to add a comment