Log mixed script shield events.

chrome/browser/content_settings/tab_specific_content_settings.h

Index: chrome/browser/content_settings/tab_specific_content_settings.h
diff --git a/chrome/browser/content_settings/tab_specific_content_settings.h b/chrome/browser/content_settings/tab_specific_content_settings.h
index 1948126ae763fc5ec33bf00db880477894180863..9df7e6de51ce8f2188fe065fcd745ac53a4afe34 100644
--- a/chrome/browser/content_settings/tab_specific_content_settings.h
+++ b/chrome/browser/content_settings/tab_specific_content_settings.h
@@ -55,6 +55,17 @@ class TabSpecificContentSettings
   static const MicrophoneCameraState CAMERA_ACCESSED = 1 << 2;
   static const MicrophoneCameraState CAMERA_BLOCKED = 1 << 3;
 
+  // UMA statistics for the mixed content shield
+  enum MixedScriptAction {
+    MIXEDSCRIPT_DISPLAYED_SHIELD = 0,
+    MIXEDSCRIPT_DISPLAYED_BUBBLE,
+    MIXEDSCRIPT_CLICKED_ALLOW,
+    MIXEDSCRIPT_CLICKED_LEARN_MORE,
+    MIXEDSCRIPT_NUM_ACTIONS

[Ilya Sherman, 2014/10/16 22:20:35]

FYI, the typical style is, if the enum name is FooBar, to have the enum values
be named FOO_BAR_APPLE, FOO_BAR_BANANA, etc.  So, in this case, I'd expect the
enum value names to start with the prefix "MIXED_SCRIPT_ACTION_".

(In theory, C++11 enum classes could provide actually namespacing, so that we
wouldn't need this ugly naming convention.  IIRC, that feature is still under
discussion on chromium-dev.)

[lgarron, 2014/10/16 22:24:30]

Man, apparently I can't get nuttin' right, even if I consult the style guide.
:-P

I consolidated MIXEDSCRIPT into one word because that's how
CONTENT_TYPE_MIXEDSCRIPT does it, but I'll change it over now.

+  };
+
+  static void RecordMixedScriptAction(MixedScriptAction action);
+
   // Classes that want to be notified about site data events must implement
   // this abstract class and add themselves as observer to the
   // |TabSpecificContentSettings|.