Presence of two password fields confuses Chrome autosave
Reported by
t.ma...@gmail.com,
May 17 2017
|
||||||
Issue descriptionChrome Version : 60.0.3095.5 OS Version: URLs (if applicable) : https://ntrade.hdfcsec.com/ Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: N/A Firefox 4.x: N/A IE 7/8/9: N/A This issue is not Linux specific. I see the same issue on my Chrome OS machine as well. What steps will reproduce the problem? 1. Open a page that has one username and two password fields, like https://ntrade.hdfcsec.com/ 2. Enter the username and passwords. 3. Chrome remembers the username and the *second* password. 4. Open the same page again. Let Chrome autofill credentials. What is the expected result? Chrome autofills the saved password into the *second* password field. What happens instead of that? Chrome remembers the first password and autofills the first password field. OR Chrome remembers the second password and autofills the second password field. Please provide any additional information below. Attach a screenshot if possible. It'll be nice if Chrome can remember and refill both passwords, but I'll be sufficiently happy if it doesn't swap the password fields. After all, not many sites use two passwords. UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3095.5 Safari/537.36
,
May 18 2017
Just for clarification: Your "What happens instead of that?" section does not mention a swapping of fields. Do you observe that?
,
May 18 2017
I messed up; sorry. This is how it should have been: What is the expected result? Chrome remembers the first password and autofills the first password field. OR Chrome remembers the second password and autofills the second password field. What happens instead of that? Chrome autofills the saved password into the *first* password field. (It saved the password from the second field.)
,
Jun 7 2017
t.manki@ - Thanks for filing the issue...!! Logging into the page at URL: https://ntrade.hdfcsec.com/, need the user to be registered and open an account. Hence, please provide any other sample URL or sample credentials to test the issue. This will help us in triaging the issue further. Thanks...!!
,
Jun 7 2017
I made a demo page here: https://m-misc.appspot.com/two-password-form. Does this look good?
,
Jun 7 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 8 2017
Thanks for the report. There are two issues: (1) As reported, Chrome should try to fill in the same field from which it saved (the fields have id attributes, so can be distinguished). (2) Chrome should ideally understand that the second field is a DOB field and ignore that (same as bug 725165).
,
Sep 8 2017
It works as expected. The forms is considered to be change password form, and it looks really like that - 2 different passwords, old and new one. Of course the second should be saved, and the first should be filled. We have some plans on making Chrome Password Manager smarter on detection forms and fields. This is good example where it could be useful.
,
Sep 8 2017
> The forms is considered to be change password form Wow, it's obvious now why Chrome behaves the way it does. Thanks! > We have some plans on making Chrome Password Manager smarter on detection forms and fields. Great. Can't wait to see the improvements :)
,
Jan 26 2018
,
Jan 26 2018
Known problem. See https://bugs.chromium.org/p/chromium/issues/detail?id=771657#c7 We will fix it with crowdsourcing. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nyerramilli@chromium.org
, May 18 2017Labels: Needs-Triage-M60