Implement Connector::ApplySpec() & use to enforce navigation:frame

services/service_manager/public/interfaces/connector.mojom

Index: services/service_manager/public/interfaces/connector.mojom
diff --git a/services/service_manager/public/interfaces/connector.mojom b/services/service_manager/public/interfaces/connector.mojom
index 63168e4a15ac5f6ae04d0991307068eda41d03de..f554765555ef27a79b87ae9b5de644a8cca4357b 100644
--- a/services/service_manager/public/interfaces/connector.mojom
+++ b/services/service_manager/public/interfaces/connector.mojom
@@ -164,4 +164,9 @@ interface Connector {
 
   // Clones this Connector so it can be passed to another thread.
   Clone(Connector& request);
+
+  ApplySpec(string spec,

[Tom Sepez, 2017/04/25 23:51:20]

I'm a little worried about parsing this (untrusted) spec in a more trusted
process.  Presently, these specs all come from manifests, and
the data is trusted.  But a renderer could pass up crafted input and force the
service manager to parse it?

[Ken Rockot(use gerrit already), 2017/04/26 00:06:33]

It's just the name of a spec. The spec itself is still looked up within the
manifest the service manager already has on hand for the service.

+            Identity source,
+            InterfaceProvider& source_request,
+            InterfaceProvider target);
 };