Password manager does not fill previously invisible form |
||||
Issue descriptionWeb site: https://gramista.com/ Password manager detects hidden form on a page (output from chrome://password-manager-internals): Form is a password form: { Action : https://gramista.com/ , New password element : password-new , Origin : https://gramista.com/ , PSL match : false, Password element : password , Password generated : false, Scheme : HTML , Signon realm : https://gramista.com/ , Times used : 0, Username element : } When "Sign-in" button is clicked, form becomes visible to the user, but the password manager doesn't detect this.
,
Jun 9 2017
Tested in beta (M60). Autofill and filling on username field doesn't work, but it works if user clicks on password field (both username and password fields are filled). So, it's not perfect but possible to fill credentials. Keep open as an example for further improvements.
,
Nov 3 2017
,
Nov 3 2017
,
Jan 26 2018
,
Jan 26 2018
All password fields on gramista.com are annotated with `autocomplete="new-password"`. Therefore, this is considered a sign-up form and not a log-in form [1]. There are tests that ensure that such fields are not filled which makes this case pretty easy to reproduce [2]. On this particular site, this behavior might be a copy-and-paste mistake as all passwords fields have the same id. They are in different pop-up containers though. [1] https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands [2] https://cs.chromium.org/chromium/src/chrome/browser/password_manager/password_manager_browsertest.cc?dr=C&q=AutofillSuggestionsForChangePwdWithEmptyNamesButOnlyNewPwdField&sq=package:chromium&l=2761 |
||||
►
Sign in to add a comment |
||||
Comment 1 by vabr@chromium.org
, Jun 8 2017Summary: Password manager does not fill previously invisible form (was: Password manager is not activate for unvisible form)