Refactor Autofill for out of process iframes (OOPIF).

components/password_manager/core/browser/password_manager.h

Index: components/password_manager/core/browser/password_manager.h
diff --git a/components/password_manager/core/browser/password_manager.h b/components/password_manager/core/browser/password_manager.h
index 3d3473d1ad979d64fdbeff5fd37ba9a892b42b29..be54d9c26a56f6ef1251d8d30e3b491de2549bde 100644
--- a/components/password_manager/core/browser/password_manager.h
+++ b/components/password_manager/core/browser/password_manager.h
@@ -49,7 +49,7 @@ class PasswordManager : public LoginModel {
 #if defined(OS_WIN)
   static void RegisterLocalPrefs(PrefRegistrySimple* registry);
 #endif
-  explicit PasswordManager(PasswordManagerClient* client);
+  PasswordManager(PasswordManagerClient* client, PasswordManagerDriver* driver);

[vabr (Chromium), 2014/11/13 14:01:33]

Oh, and actually, having one PasswordManager per frame rather than page is a big
change. Currently it aggregates password form information from all frames, so
isolating that would certainly change its behaviour.

At a first shot it looks to me like there should be exactly one PasswordManager
for one PasswordManagerClient, and it should get access to the driver factory
instead of to particular drivers.

But I'll need to think about this more. Will update this CL if I find reason
against having managers to clients 1:1.

   ~PasswordManager() override;
 
   typedef base::Callback<void(const autofill::PasswordForm&)>