| commit | c57dd5602fee1bc2fa1df2424c5f7b95a1702cf4 | |
| author | gcasto <gcasto@chromium.org> | |
| Tue, 28 Oct 2014 00:45:43 +0000 (27 17:45 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Tue, 28 Oct 2014 00:46:18 +0000 (28 00:46 +0000) | ||
| tree | 68bb1951ce2f5dfeb46022175aae915fe0b6effd | treesnapshot (tar.gz zip) |
| parent | 0823191b969a7c37625e62e1ec23091b7c40f6a1 | commitdiff |
[Password Generation] Always query password forms via Autofill
For other fields, we assume that if the author has specified autocomplete
attributes we should respect all their choices, including not trying to
determine field autocomplete values for fields that the author didn't specify.
This doesn't apply for password fields for two reasons. First, there is no way
for an author to specify generation for a particular field. Second, since
generation isn't a specced autocomplete value, the password field can reasonably
be set (e.g. "autocomplete=new-password") and also have generation enabled.
BUG=424793
Review URL: https://codereview.chromium.org/659793005
Cr-Commit-Position: refs/heads/master@{#301521}
For other fields, we assume that if the author has specified autocomplete
attributes we should respect all their choices, including not trying to
determine field autocomplete values for fields that the author didn't specify.
This doesn't apply for password fields for two reasons. First, there is no way
for an author to specify generation for a particular field. Second, since
generation isn't a specced autocomplete value, the password field can reasonably
be set (e.g. "autocomplete=new-password") and also have generation enabled.
BUG=424793
Review URL: https://codereview.chromium.org/659793005
Cr-Commit-Position: refs/heads/master@{#301521}