Focus should be moved to the next input field after we generate the password.

chrome/renderer/autofill/password_generation_manager.cc

Index: chrome/renderer/autofill/password_generation_manager.cc
diff --git a/chrome/renderer/autofill/password_generation_manager.cc b/chrome/renderer/autofill/password_generation_manager.cc
index ac937607972b59d44288add572cc93f4b96ad5e3..34cb027dd260d86b5c0a295dc110df6fe360dfcb 100644
--- a/chrome/renderer/autofill/password_generation_manager.cc
+++ b/chrome/renderer/autofill/password_generation_manager.cc
@@ -56,8 +56,9 @@ bool GetAccountCreationPasswordFields(
 PasswordGenerationManager::PasswordGenerationManager(
     content::RenderView* render_view)
     : content::RenderViewObserver(render_view),
+      render_view_(render_view),
       enabled_(false) {
-  render_view->GetWebView()->addTextFieldDecoratorClient(this);
+  render_view_->GetWebView()->addTextFieldDecoratorClient(this);
 }
 PasswordGenerationManager::~PasswordGenerationManager() {}
 
@@ -190,6 +191,9 @@ void PasswordGenerationManager::OnPasswordAccepted(const string16& password) {
     it->setValue(password);
     it->setAutofilled(true);
   }
+  // Advance focus to the input field next to the two password fields.

[Garrett Casto, 2012/06/28 21:27:13]

This isn't guaranteed to be 2 password fields in the feature. Can you just put
this in the above loop so that this gets called the correct number of times when
we start changing the heuristics.

Also, we may want to note that this assumes that the passwords fields are
adjacent. I haven't seen a case where this isn't true yet, so it's probably a
reasonable assumption.

[zysxqn, 2012/06/28 22:57:16]

Done.

+  render_view_->GetWebView()->advanceFocus(false);
+  render_view_->GetWebView()->advanceFocus(false);
 }
 
 void PasswordGenerationManager::OnPasswordGenerationEnabled(bool enabled) {