[SiteChip] Add UMA, finish wiring site chip experiment up to the omnibox.

chrome/browser/ui/views/toolbar/site_chip_view.cc

Index: chrome/browser/ui/views/toolbar/site_chip_view.cc
diff --git a/chrome/browser/ui/views/toolbar/site_chip_view.cc b/chrome/browser/ui/views/toolbar/site_chip_view.cc
index 790a2dd29789ee3b6f9c3c9bd30808d38927fff6..86ade3d76f035a0dc8f3b5e4c650c6ca94e96662 100644
--- a/chrome/browser/ui/views/toolbar/site_chip_view.cc
+++ b/chrome/browser/ui/views/toolbar/site_chip_view.cc
@@ -5,6 +5,7 @@
 #include "chrome/browser/ui/views/toolbar/site_chip_view.h"
 
 #include "base/files/file_path.h"
+#include "base/metrics/histogram.h"
 #include "base/prefs/pref_service.h"
 #include "base/strings/string_util.h"
 #include "base/strings/utf_string_conversions.h"
@@ -29,6 +30,7 @@
 #include "chrome/common/extensions/manifest_handlers/icons_handler.h"
 #include "chrome/common/pref_names.h"
 #include "chrome/common/url_constants.h"
+#include "content/public/browser/user_metrics.h"
 #include "content/public/browser/web_contents.h"
 #include "content/public/common/url_constants.h"
 #include "extensions/common/constants.h"
@@ -440,10 +442,13 @@ void SiteChipView::OnPaint(gfx::Canvas* canvas) {
 // this button.
 void SiteChipView::ButtonPressed(views::Button* sender,
                                  const ui::Event& event) {
+  UMA_HISTOGRAM_COUNTS("SiteChip.Pressed", 1);

[msw, 2013/12/12 00:17:49]

What are you trying to record? This will do a decent job of recording the number
of times a single user has clicked the SiteChip, and presenting that locally at
about:histograms. But, you'll need to modify
tools/metrics/histograms/histograms.xml to get this shown correctly on the UMA
dashboard and aggregated for respondant Chrome users, and this format isn't good
for that type of data collection anyway (you'd just see the aggregate number of
times users have clicked the site chip, not a distribution of how many times
each user clicks the button in a given session or anything). Also, this number
alone doesn't give much context, you might want to record the number of
SiteChips made visible and/or updated, how many times any are hovered, or
something else that would give this a frame of reference.

[Greg Billock, 2013/12/12 20:36:37]

Yeah, I'll add the histograms.xml descriptor separately. Measuring hover is
probably a good plan. I don't know that we really have a plan for what we'd do
with measurements like per-user per-session clicks or something. We want to
measure usage, but we don't expect much interaction, so it's not clear what we'd
do with more information.

+  content::RecordAction(content::UserMetricsAction("SiteChipPress"));
   toolbar_view_->location_bar()->GetOmniboxView()->SetFocus();

[msw, 2013/12/12 00:17:49]

nit: make a local OmniboxView* omnibox_view =
toolbar_view_->location_bar()->GetOmniboxView(); for convenience here.

[Greg Billock, 2013/12/12 20:36:37]

After Justin's change, we won't need SetFocus, and probably not
SetCaretVisibility either. I'm planning to delete those lines at some point.

-  toolbar_view_->location_bar()->GetOmniboxView()->SelectAll(true);
   toolbar_view_->location_bar()->GetOmniboxView()->model()->
       SetCaretVisibility(true);
+  toolbar_view_->location_bar()->GetOmniboxView()->ShowURL();
+  //toolbar_view_->location_bar()->GetOmniboxView()->SelectAll(true);

[msw, 2013/12/12 00:17:49]

Remove this.

[Greg Billock, 2013/12/12 20:36:37]

Done.

 }
 
 void SiteChipView::WriteDragDataForView(View* sender,