Autofill passwords after re-opening tab containing a login page.

chrome/renderer/autofill/password_autofill_manager_unittest.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "base/string_util.h"
 #include "base/utf_string_conversions.h"
 #include "chrome/common/autofill_messages.h"
 #include "chrome/renderer/autofill/autofill_agent.h"
 #include "chrome/renderer/autofill/password_autofill_manager.h"
 #include "chrome/test/render_view_test.h"
@@ skipping 185 matching lines @@
   */
 
   // Simulate the browser sending back the login info, it triggers the
   // autocomplete.
   SimulateOnFillPasswordForm(fill_data_);
 
   // The username and password should have been autocompleted.
   CheckTextFieldsState(kAliceUsername, true, kAlicePassword, true);
 }
 
-// Tests that having a non-empty username precludes the autocomplete.
+// Tests that we correctly fill forms having an empty 'action' attribute.
 TEST_F(PasswordAutofillManagerTest, InitialAutocompleteForEmptyAction) {
   const char kEmptyActionFormHTML[] =
       "<FORM name='LoginTestForm'>"
       "  <INPUT type='text' id='username'/>"
       "  <INPUT type='password' id='password'/>"
       "  <INPUT type='submit' value='Login'/>"
       "</FORM>";
   LoadHTML(kEmptyActionFormHTML);
 
   // Retrieve the input elements so the test can access them.
@@ skipping 27 matching lines @@
 
   // Simulate the browser sending back the login info, it triggers the
   // autocomplete.
   SimulateOnFillPasswordForm(fill_data_);
 
   // Only the username should have been autocompleted.
   // TODO(jcivelli): may be we should not event fill the username?
   CheckTextFieldsState(kAliceUsername, true, "", false);
 }
 
-// Tests that having a non-empty username precludes the autocomplete.
+// Tests that having a non-matching username precludes the autocomplete.
 TEST_F(PasswordAutofillManagerTest, NoInitialAutocompleteForFilledField) {
   username_element_.setValue(WebString::fromUTF8("bogus"));
 
   // Simulate the browser sending back the login info, it triggers the
   // autocomplete.
   SimulateOnFillPasswordForm(fill_data_);
 
   // Neither field should be autocompleted.
   CheckTextFieldsState("bogus", false, "", false);
 }
 
+// Tests that having a matching username does not preclude the autocomplete.
+TEST_F(PasswordAutofillManagerTest, InitialAutocompleteForMatchingFilledField) {
+  username_element_.setValue(WebString::fromUTF8(kAliceUsername));
+
+  // Simulate the browser sending back the login info, it triggers the
+  // autocomplete.
+  SimulateOnFillPasswordForm(fill_data_);
+
+  // The username and password should have been autocompleted.
+  CheckTextFieldsState(kAliceUsername, true, kAlicePassword, true);
+}
+
 // Tests that editing the password clears the autocompleted password field.
 TEST_F(PasswordAutofillManagerTest, PasswordClearOnEdit) {
   // Simulate the browser sending back the login info, it triggers the
   // autocomplete.
   SimulateOnFillPasswordForm(fill_data_);
 
   // Simulate the user changing the username to some unknown username.
   SimulateUsernameChange("alicia", true);
 
   // The password should have been cleared.
@@ skipping 123 matching lines @@
   // To simulate accepting an item in the suggestion drop-down we just mimic
   // what the WebView does: it sets the element value then calls
   // didSelectAutoFillSuggestion on the renderer.
   autofill_agent_->didSelectAutoFillSuggestion(username_element_,
                                                ASCIIToUTF16(kAliceUsername),
                                                WebKit::WebString(),
                                                0);
   // Autocomplete should not have kicked in.
   CheckTextFieldsState("", false, "", false);
 }