Suggest to fill password change forms

components/autofill/content/renderer/password_autofill_agent.cc

Index: components/autofill/content/renderer/password_autofill_agent.cc
diff --git a/components/autofill/content/renderer/password_autofill_agent.cc b/components/autofill/content/renderer/password_autofill_agent.cc
index ea8944a26a098cfda0842c0c72e8096fd047d984..3bc6763ed01317b249609274c4cb0109d28e0b56 100644
--- a/components/autofill/content/renderer/password_autofill_agent.cc
+++ b/components/autofill/content/renderer/password_autofill_agent.cc
@@ -858,7 +858,9 @@ bool PasswordAutofillAgent::ShowSuggestions(
   // is no username or the corresponding username element is not editable since
   // it is only in that case that the username element does not have a
   // suggestions popup.
-  if (element.isPasswordField() && username_is_available)
+  if (element.isPasswordField() &&
+      !password_info->fill_data.is_password_change_form &&

[Garrett Casto, 2015/06/05 21:22:30]

Is this because we don't trust that |username_element| is correct for change
password forms? I seem to remember this being a problem somewhere, maybe
twitter? Given the other changes this will make it so that a lot of signup forms
will show a saved password when you click on them, though that probably isn't a
huge deal.

[dvadym, 2015/06/09 16:40:08]

Yeah, we will not trust username element and show suggestions for both username
(if present) and password fields. The Facebook password change form has
additional invisible field, that we can't distinguish from username.

+      username_is_available)
     return true;
 
   // Chrome should never show more than one account for a password element since