Allow the browser to choose PasswordManager's authorization prompt policy.

components/password_manager/core/browser/password_manager.cc

Index: components/password_manager/core/browser/password_manager.cc
diff --git a/components/password_manager/core/browser/password_manager.cc b/components/password_manager/core/browser/password_manager.cc
index a3f6f5c9cc198f18c6a543c1882d73473d39fafe..cf6ef7dab13cec0dd7f3bd050503b4f6f8953df5 100644
--- a/components/password_manager/core/browser/password_manager.cc
+++ b/components/password_manager/core/browser/password_manager.cc
@@ -373,18 +373,8 @@ void PasswordManager::CreatePendingLoginManagers(
         new PasswordFormManager(this, client_, driver_, *iter, ssl_valid);
     pending_login_managers_.push_back(manager);
 
-    // Password Autofill is supposed to be a convenience. If it creates a
-    // blocking dialog, it is no longer convenient. We should only prompt the
-    // user after a full username has been typed in. Until that behavior is
-    // implemented, never prompt the user for keychain access.
-    // Effectively, this means that passwords stored by Chrome still work,
-    // since Chrome can access those without a prompt, but passwords stored by
-    // Safari, Firefox, or Chrome Canary will not work. Note that the latest
-    // build of Safari and Firefox don't create keychain items with the
-    // relevant tags anyways (7/11/2014).
-    // http://crbug.com/178358
     PasswordStore::AuthorizationPromptPolicy prompt_policy =
-        PasswordStore::DISALLOW_PROMPT;
+        client_->GetAuthorizationPromptPolicy(*iter);
 
     manager->FetchMatchingLoginsFromPasswordStore(prompt_policy);
   }