Improving filling of password field in Password Manager |
|||
Issue descriptionThere is quite tricky logic in Password Manager for finding fields for choosing fields for filling username/password. And it could fail by many reasons, for example 1.The page has invisible password field and it's not possible to check that it's invisible and Password Manager fills it instead of real password field. 2.JavaScript makes some tricky changes in a form or fields and Password Manager fails to understand it correctly. But Password Manager could do it better for password field. This issue is for improving Password Manager logic to do this.
,
May 24 2016
Issue 393482 has been merged into this issue.
,
Feb 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a6ea9dfa43640a82f3c7d07da387d67d485db1c8 commit a6ea9dfa43640a82f3c7d07da387d67d485db1c8 Author: dvadym <dvadym@chromium.org> Date: Mon Feb 27 11:47:59 2017 More robust fill password fields on click. Originally, Chrome would only offer suggestions for password fields, when no username were found. Since https://codereview.chromium.org/1814193002, it also offers suggestions when the user clicks on any password field. However, if JavaScript changes field names immediately after load, before password fill data reach the renderer, Chrome still fails to display suggestions. This CL changes PasswordAutofillAgent to use password field data even if fields names were changed. That allows Chrome to show suggestions even in the above mentioned problematic case. BUG= 597304 Review-Url: https://codereview.chromium.org/2716873002 Cr-Commit-Position: refs/heads/master@{#453193} [modify] https://crrev.com/a6ea9dfa43640a82f3c7d07da387d67d485db1c8/chrome/renderer/autofill/password_autofill_agent_browsertest.cc [modify] https://crrev.com/a6ea9dfa43640a82f3c7d07da387d67d485db1c8/components/autofill/content/renderer/password_autofill_agent.cc
,
Feb 27 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Apr 8 2016