Issue metadata
Sign in to add a comment
|
Id code field is recognized as username field on chaseonline.chase.com |
||||||||||||||||||||||
Issue description1. 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)
,
Jun 1 2016
,
Jun 1 2016
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.
,
Jun 7 2016
,
Mar 8 2017
,
May 24 2017
,
May 24 2018
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
,
Jun 1 2018
,
Oct 25
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted