Add a test for toggling logging in PasswordAutofillAgent

components/autofill/content/renderer/test_password_autofill_agent.h

Index: components/autofill/content/renderer/test_password_autofill_agent.h
diff --git a/components/autofill/content/renderer/test_password_autofill_agent.h b/components/autofill/content/renderer/test_password_autofill_agent.h
index 01f5a4b07387e444cc571f07d77320a95c581348..72da5784da79157cb46cead65efb4e123c9e90a5 100644
--- a/components/autofill/content/renderer/test_password_autofill_agent.h
+++ b/components/autofill/content/renderer/test_password_autofill_agent.h
@@ -14,6 +14,8 @@ class TestPasswordAutofillAgent : public PasswordAutofillAgent {
   explicit TestPasswordAutofillAgent(content::RenderView* render_view);
   virtual ~TestPasswordAutofillAgent();
 
+  using PasswordAutofillAgent::logging_state_active;

[tfarina, 2014/04/25 16:04:56]

just curious, what is this? I never saw we doing this before.

[vabr (Chromium), 2014/04/25 16:52:27]

That means that logging_state_active from PasswordAutofillAgent appears in the
TestPasswordAutofillAgent "namespace".
The reason is to change its visibility from protected (in PasswordAutofillAgent)
to public here.
Equivalent but longer notation would be to override logging_state_active and
make it call the PasswordAutofillAgent version directly.

See Effective C++, 3rd edition, Item 33, by Scott Meyers.
(In my case it was: see the above, forget about it, and then have Ilya re-teach
me that. :))

+
  private:
   // Always returns true. This allows browser tests with "data: " URL scheme to
   // work with the password manager.