Add a feature flag for the security verbose

testing/variations/fieldtrial_testing_config.json

Index: testing/variations/fieldtrial_testing_config.json
diff --git a/testing/variations/fieldtrial_testing_config.json b/testing/variations/fieldtrial_testing_config.json
index 5abdf95fc9f9fe96ae0bd87cfd4e88b304bc5007..f51355e2e13393b5f11e4ade605c0e3b7eafc015 100644
--- a/testing/variations/fieldtrial_testing_config.json
+++ b/testing/variations/fieldtrial_testing_config.json
@@ -1769,6 +1769,28 @@
             ]
         }
     ],
+    "SecurityChip": [
+        {
+            "platforms": [
+                "chromeos",
+                "linux",
+                "mac",
+                "win"
+            ],
+            "experiments": [
+                {
+                    "name": "Enabled",
+                    "params": {
+                        "animation": "animate-all",
+                        "visibility": "show-all"
+                    },
+                    "enable_features": [
+                        "SecurityChip"
+                    ]
+                }
+            ]
+        }
+    ],

[Ilya Sherman, 2016/10/24 23:37:01]

Is there an active field trial (or a soon-to-be-active field trial) for this
experiment?  If not, then there's no need to land this config yet.  I didn't
find one via code search, but LGTM if this matches a config that you're about to
land.

[estark, 2016/10/25 17:02:02]

I think the plan is to create an active field trial as soon as this lands. Does
that sound right to you, spqchan?

     "SecurityWarningIconUpdate": [
         {
             "platforms": [