Implement API for accessing fonts installed locally on the system.

content/browser/renderer_host/render_process_host_impl.cc

Index: content/browser/renderer_host/render_process_host_impl.cc
diff --git a/content/browser/renderer_host/render_process_host_impl.cc b/content/browser/renderer_host/render_process_host_impl.cc
index e5a1a986811b3e28f6a286d0cd0140bf9a2880c2..0fdb1bb71087cf1efba45ca1228b5afe81c80681 100644
--- a/content/browser/renderer_host/render_process_host_impl.cc
+++ b/content/browser/renderer_host/render_process_host_impl.cc
@@ -61,6 +61,7 @@
 #include "content/browser/dom_storage/dom_storage_message_filter.h"
 #include "content/browser/fileapi/chrome_blob_storage_context.h"
 #include "content/browser/fileapi/fileapi_message_filter.h"
+#include "content/browser/font_access/font_access_service_impl.h"
 #include "content/browser/frame_host/render_frame_message_filter.h"
 #include "content/browser/geofencing/geofencing_dispatcher_host.h"
 #include "content/browser/gpu/browser_gpu_memory_buffer_manager.h"
@@ -1070,6 +1071,9 @@ void RenderProcessHostImpl::RegisterMojoServices() {
 #endif
 
   mojo_application_host_->service_registry()->AddService(
+      base::Bind(&FontAccessServiceImpl::Create));

[ncarter (slow), 2016/02/09 18:59:45]

I'd like to see some browser tests (or layout tests) that exercise the
content/browser part of this change.

[Daniel Nishi, 2016/02/11 00:23:50]

Which part are we looking to get under the test harness with a browser/layout
test? The content/browser portion is unit-tested, so are we trying to test the
service registry layer?

+
+  mojo_application_host_->service_registry()->AddService(
       base::Bind(&PermissionServiceContext::CreateService,
                  base::Unretained(permission_service_context_.get())));