Add UMA for autoblocking and embargoing.

chrome/browser/permissions/permission_context_base.cc

Index: chrome/browser/permissions/permission_context_base.cc
diff --git a/chrome/browser/permissions/permission_context_base.cc b/chrome/browser/permissions/permission_context_base.cc
index c00f3e7aa503570ad94c778a64b0b4923857aa9d..6f6da89a5c28183f8e2f73378915ef849d5d0288 100644
--- a/chrome/browser/permissions/permission_context_base.cc
+++ b/chrome/browser/permissions/permission_context_base.cc
@@ -289,6 +289,8 @@ void PermissionContextBase::PermissionDecided(
     const BrowserPermissionCallback& callback,
     bool persist,
     ContentSetting content_setting) {
+  PermissionUmaUtil::RecordPermissionEmbargoReason(

[dominickn, 2017/01/30 02:41:36]

Nit: add a comment saying:

// If a decision was made, the request cannot have been embargoed.

[meredithl, 2017/01/30 03:52:17]

Done.

+      PermissionEmbargoReason::NOT_EMBARGOED);

[dominickn, 2017/01/30 02:41:36]

You need to move this into an else case on line 321 (otherwise when a prompt
dismissal is embargoed, we'll double count a NOT_EMBARGOED and a
REPEATED_DISMISSAL).

You can add a test for that too (check the embargo histogram after repeated
dismissal). That should just involve adding a histogram check in the existing
repeated dismissal tests.

[meredithl, 2017/01/30 03:52:17]

Done.

   if (PermissionRequestManager::IsEnabled()) {
     // Infobar persistence and its related UMA is tracked on the infobar
     // controller directly.