Suggest to fill password change forms

components/autofill/core/common/password_form_fill_data.h

Index: components/autofill/core/common/password_form_fill_data.h
diff --git a/components/autofill/core/common/password_form_fill_data.h b/components/autofill/core/common/password_form_fill_data.h
index 0eea16fbd87dae9c008970989316560f2306d819..4aee125adef373dc26cf9ad4bdbfe5df741e3161 100644
--- a/components/autofill/core/common/password_form_fill_data.h
+++ b/components/autofill/core/common/password_form_fill_data.h
@@ -76,6 +76,9 @@ struct PasswordFormFillData {
   // and our saved representation don't match up.
   bool wait_for_username;
 
+  // True if this form is a password change form.
+  bool is_password_change_form;

[Garrett Casto, 2015/06/09 23:56:22]

Given that PasswordFormManager already has both
is_ignoreable_change_password_form and is_change_password_form, perhaps this
should be named something else (is_possible_change_password_form)? At the moment
it seems pretty strange that |is_password_change_form| can be true but
|is_change_password_form| that we compute in PasswordFormManager is false. They
are used for different things (saving vs. filling) so I understand why, but it's
still confusing.

[dvadym, 2015/06/10 14:22:03]

Thanks, I didn't know about |is_change_password_form| in PasswordFormManager.
I've changed calculation |is_change_password_form| to call
PasswordForm::IsChangePasswordForm, it seems to be normal to use the same
condition for checking change password form in all places. What do you think? 

+
   PasswordFormFillData();
   ~PasswordFormFillData();
 };