Add new Content settings type AUTO-SUBMIT-CERTIFICATE

chrome/common/chrome_switches.cc

Index: chrome/common/chrome_switches.cc
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 5f6ec9eb257211f02df011a2a72550fad3ee48e4..a9592cdd4e2b766f5b05346851f0464b3d281d58 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -389,6 +389,8 @@ const char kEnableAuthNegotiatePort[]       = "enable-auth-negotiate-port";
 // automatically due to privacy concerns.
 const char kEnableAutofillFeedback[]        = "enable-autofill-feedback";
 
+const char kEnableAutoSubmitCertificate[]   = "enable-auto-submit-certificate";

[Mattias Nissler (ping if slow), 2011/08/09 15:37:25]

What's the reason we develop this behind a flag? It has no user-facing UI
anyway.

[wtc, 2011/08/11 18:33:55]

Add a comment to explain what this command-line option means.

[markusheintz_, 2011/08/15 19:09:04]

@mnissler: I thought it might be good to have a switch to turn the policy off.
But you are right. I removed the switch again since we do not really need it.

[markusheintz_, 2011/08/15 19:09:04]

I decided to remove the switch.

+
 // This flag enables UI for clearing server data.  Temporarily in place
 // until there's a server endpoint deployed.
 const char kEnableClearServerData[]         = "enable-clear-server-data";