This CL does the following: (1) Pass the max_length attribute to the password generator; (2) Update…

chrome/browser/autofill/autofill_manager.cc

Index: chrome/browser/autofill/autofill_manager.cc
diff --git a/chrome/browser/autofill/autofill_manager.cc b/chrome/browser/autofill/autofill_manager.cc
index 146c42923b90c724f4d569dc38f407cb45adf0ce..ceb325b0f383473a29fc75644f8d5b7c65d675ab 100644
--- a/chrome/browser/autofill/autofill_manager.cc
+++ b/chrome/browser/autofill/autofill_manager.cc
@@ -28,6 +28,7 @@
 #include "chrome/browser/autofill/autofill_type.h"
 #include "chrome/browser/autofill/credit_card.h"
 #include "chrome/browser/autofill/form_structure.h"
+#include "chrome/browser/autofill/password_generator.h"
 #include "chrome/browser/autofill/personal_data_manager.h"
 #include "chrome/browser/autofill/personal_data_manager_factory.h"
 #include "chrome/browser/autofill/phone_number.h"
@@ -717,13 +718,17 @@ void AutofillManager::OnHideAutofillPopup() {
     external_delegate_->HideAutofillPopup();
 }
 
-void AutofillManager::OnShowPasswordGenerationPopup(const gfx::Rect& bounds) {
+void AutofillManager::OnShowPasswordGenerationPopup(const gfx::Rect& bounds,
+                                                    int max_length) {
 #if defined(OS_ANDROID)
   NOTIMPLEMENTED();
 #else
   Browser* browser = browser::FindLastActiveWithProfile(
       Profile::FromBrowserContext(web_contents()->GetBrowserContext()));
-  browser->window()->ShowPasswordGenerationBubble(bounds);
+  scoped_ptr<autofill::PasswordGenerator> password_generator(
+      new autofill::PasswordGenerator(max_length));

[Ilya Sherman, 2012/06/01 01:09:55]

This will be deleted immediately at the end of the function, which is probably
not what you wanted, right?  If that's not a problem, I would skip the
heap-allocation and just declare the PasswordGenerator on the stack.

[zysxqn, 2012/06/01 19:01:32]

I don't think it's a problem here. Only when user click the generation icon on
the password form again do we need to re-show the bubble and re-generate the
password, and this will be done by create a new bubble and a new password
generator.

Changed to stack allocation.

[Garrett Casto, 2012/06/01 20:02:02]

I don't think that either of these solutions is really what you want. The only
reason that this happens to work right now is that we are generating the
password in the constructor. When we add the button to regenerate passwords this
is going to segfault. Either you shouldn't store the PasswordGenerator as a
member variable, or you should heap allocate here and grab with a scoped_ptr in
the bubbles. I prefer the latter since I think that we are going to want the
ability to regenerate passwords eventually.

[zysxqn, 2012/06/01 22:32:54]

Done.

+  browser->window()->ShowPasswordGenerationBubble(
+      bounds, password_generator.get());
 #endif  // #if defined(OS_ANDROID)
 }