Recognise second hinted new-password field as confirmation
Chrome can see multiple hints from the server that a field is a new-password field. This happens, in particular, if two fields have the same name and hence the same signature -- because server hints are keyed by the signature, there is no way to specify two different types for two fields with the same name. If there is no other explicitly hinted confirmation field, then it is likely that in reality one of the new-password fields was supposed to be a confirmation field. Knowing which field is the confirmation field will be useful for Chrome to understand where to copy the generated password to. Therefore, this CL makes sure that the second hinted same-signature new-password field is marked as a confirmation field, unless the server also explicitly hints that some field is a confirmation field. This is analogous to what the parser already does in case of two fields with the autocomplete="new-password" attribute. Bug: 902700 Change-Id: I06e75a6d1059976c68d04903351d9bd207de2ee9 Reviewed-on: https://chromium-review.googlesource.com/c/1326511 Commit-Queue: Vaclav Brozek <vabr@chromium.org> Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#608818}
Showing
Please register or sign in to comment