Updating of all entries in PasswordManager of the same credentials on password update

components/password_manager/core/browser/credential_manager_pending_request_task.cc

Index: components/password_manager/core/browser/credential_manager_pending_request_task.cc
diff --git a/components/password_manager/core/browser/credential_manager_pending_request_task.cc b/components/password_manager/core/browser/credential_manager_pending_request_task.cc
index 23ffc12060321266e389ee994ebf894e55b479b6..6223ffcbd3f2b5308e28b1e31de3055c151ce120 100644
--- a/components/password_manager/core/browser/credential_manager_pending_request_task.cc
+++ b/components/password_manager/core/browser/credential_manager_pending_request_task.cc
@@ -69,13 +69,9 @@ void CredentialManagerPendingRequestTask::OnGetPasswordStoreResults(
     // TODO(mkwst): This doesn't create a PasswordForm that we can use to create
     // a FederatedCredential (via CreatePasswordFormFromCredentialInfo). We need
     // to fix that.
-    ScopedVector<autofill::PasswordForm> more_local_results(
-        AffiliatedMatchHelper::TransformAffiliatedAndroidCredentials(
-            delegate_->GetSynthesizedFormForOrigin(),
-            affiliated_results.Pass()));
-    local_results.insert(local_results.end(), more_local_results.begin(),
-                         more_local_results.end());
-    more_local_results.weak_clear();
+    local_results.insert(local_results.end(), affiliated_results.begin(),

[vasilii, 2015/09/25 14:16:15]

This is definitely a right thing to do. I got a bug report few days ago where a
user couldn't delete an android credential from the bubble.

+                         affiliated_results.end());
+    affiliated_results.weak_clear();
   }
 
   if ((local_results.empty() && federated_results.empty())) {