Add a feature flag for the security verbose

chrome/common/chrome_features.cc

Index: chrome/common/chrome_features.cc
diff --git a/chrome/common/chrome_features.cc b/chrome/common/chrome_features.cc
index ae6adbbd4f1739245dbc21ac79b681bbbcec0a8f..2bd7499e9954bd61edc64445dc45bd68b791a2d0 100644
--- a/chrome/common/chrome_features.cc
+++ b/chrome/common/chrome_features.cc
@@ -138,6 +138,11 @@ const base::Feature kRunAllFlashInAllowMode{"RunAllFlashInAllowMode",
 const base::Feature kSafeSearchUrlReporting{"SafeSearchUrlReporting",
                                             base::FEATURE_DISABLED_BY_DEFAULT};
 
+#if !defined(OS_ANDROID) && !defined(OS_IOS)
+extern const base::Feature kSecurityChipFeature{

[estark, 2016/10/21 20:32:27]

nit: this should have a comment above explaining it, something along the lines
of:

// Enables or disables security chips in the omnibox that show verbose
explanations for security states.

[estark, 2016/10/21 20:32:27]

nit: I don't think you need `extern` here (only in the .h)

[spqchan, 2016/10/21 21:57:06]

Done.

[spqchan, 2016/10/21 21:57:06]

Done.

+    "SecurityChipFeature", base::FEATURE_DISABLED_BY_DEFAULT};
+#endif
+
 // A new user experience for transitioning into fullscreen and mouse pointer
 // lock states.
 const base::Feature kSimplifiedFullscreenUI{"ViewsSimplifiedFullscreenUI",