[GRC] UKM Support

content/public/app/mojo/content_browser_manifest.json

Index: content/public/app/mojo/content_browser_manifest.json
diff --git a/content/public/app/mojo/content_browser_manifest.json b/content/public/app/mojo/content_browser_manifest.json
index 0326e8616e2d1a1a47742500b24d4a10cec5930c..8432dbe8b8cfb36fc3bbaaacfb4b6112a9491f89 100644
--- a/content/public/app/mojo/content_browser_manifest.json
+++ b/content/public/app/mojo/content_browser_manifest.json
@@ -57,8 +57,10 @@
       },
       "requires": {
         "*": [ "app" ],
+	// TODO(matthalp,oysteine,holte) isolate ukm capabilities from the render

[dcheng, 2017/06/23 16:10:35]

Nit: 80 chars please (same below)

[matthalp, 2017/06/23 16:36:28]

Done.

+	// capabilities and then replace the render capabilities with them
         // In classic ash, the browser supplies ash interfaces to itself.
-        "content_browser": [ "ash", "display", "memory_instrumentation" ],
+        "content_browser": [ "ash", "display", "memory_instrumentation", "renderer" ],

[dcheng, 2017/06/23 16:10:35]

Maybe we should split the renderer capability to be a little more fine-grained?
Is that possible to do here without having to refactor everything?

[matthalp, 2017/06/23 16:36:28]

holte@ what do you think? I am not sure what entities strictly use
content_browser:renderer solely for access to UKM.

[Steven Holte, 2017/06/23 18:11:02]

AFAIK nothing has actually started using the UKM mojo interface yet, so you can
freely move it into a new capability.

         "content_gpu": [ "browser" ],
         "content_plugin": [ "browser" ],
         "content_renderer": [ "browser" ],
@@ -83,9 +85,8 @@
           "barcode_detection",
           "face_detection",
           "text_detection"
-
         ],
-        "resource_coordinator": [ "coordination_unit" ],
+        "resource_coordinator": [ "coordination_unit", "service_callbacks" ],
         "video_capture": [ "capture", "tests" ]
       }
     },