[GRC] UKM Support

chrome/browser/chrome_content_browser_manifest_overlay.json

Index: chrome/browser/chrome_content_browser_manifest_overlay.json
diff --git a/chrome/browser/chrome_content_browser_manifest_overlay.json b/chrome/browser/chrome_content_browser_manifest_overlay.json
index 357898da13e34256451b7e07f2a0193d5028b7d3..2b07dd54eaf802aa198bfff51e4ad3595615767c 100644
--- a/chrome/browser/chrome_content_browser_manifest_overlay.json
+++ b/chrome/browser/chrome_content_browser_manifest_overlay.json
@@ -17,7 +17,9 @@
           "spellcheck::mojom::SpellCheckHost",
           "spellcheck::mojom::SpellCheckPanelHost",
           "startup_metric_utils::mojom::StartupMetricHost",
-          "translate::mojom::ContentTranslateDriver",
+          "translate::mojom::ContentTranslateDriver"
+	],

[dcheng, 2017/06/23 21:32:32]

Tab =)

[matthalp, 2017/06/23 21:56:13]

Thanks for catching this. It didn't show up in my editor.

+        "ukm": [

[dcheng, 2017/06/23 21:32:32]

I think it's worth expanding the capability name to be url_keyed_metrics (it's a
bit cryptic as it is)

Also, don't things that used to ukm implicitly through renderer need to have
their manifests updated as well?

[matthalp, 2017/06/23 21:56:13]

Using url_keyed_metrics instead of ukm makes sense to me -- done.

This is the first CL to use the UkmRecorderInterface so there are no additional
manifests to update:
https://cs.chromium.org/search/?q=ukm::mojom::UkmRecorderInterfacePtr+package...

           "ukm::mojom::UkmRecorderInterface"
         ],
         "gpu": [