[Password Manager] Don't upload FIRST_USE vote for new passwords
When a credential is used for the first time, we upload a FIRST_USE crowdsourcing vote, voting the fields as USERNAME and PASSWORD, even if the use results in a new password value being saved. This was to be resilient against cases where the password manager saves the wrong password in the original form. However, it is semantically incorrect, both in the above case and also when applied to change-password forms. We change the vote so that we don't upload a vote for the password field. This does not apply to usernames, because a new username is treated as a new credential. In the case where we add a username to an old credential, we keep setting the KNOWN_VALUE flag, because this event only happens as a correction and doesn't say something different about the field. Also, the fact that the user accepted the prompt is a strong indication that the field contains a proper username. Bug: 840384 Change-Id: Iff20a022abc50a4dab2f32f46e13e33621eb6129 Reviewed-on: https://chromium-review.googlesource.com/1071523 Commit-Queue: Christos Froussios <cfroussios@chromium.org> Reviewed-by:Maxim Kolosovskiy <kolos@chromium.org> Cr-Commit-Position: refs/heads/master@{#561870}
Showing
Please register or sign in to comment