Add Android implementation of navigator.getInstalledRelatedApps.

content/public/android/java/src/org/chromium/content/browser/InterfaceRegistrarImpl.java

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 package org.chromium.content.browser;
 
 import android.content.Context;
 
 import org.chromium.base.annotations.CalledByNative;
 import org.chromium.base.annotations.JNINamespace;
 import org.chromium.content.browser.androidoverlay.AndroidOverlayProviderImpl;
+import org.chromium.content.browser.installedapp.InstalledAppProviderFactory;
 import org.chromium.content.browser.shapedetection.FaceDetectionProviderImpl;
 import org.chromium.content_public.browser.InterfaceRegistrar;
 import org.chromium.content_public.browser.RenderFrameHost;
 import org.chromium.content_public.browser.WebContents;
 import org.chromium.device.BatteryMonitor;
 import org.chromium.device.battery.BatteryMonitorFactory;
 import org.chromium.device.mojom.VibrationManager;
 import org.chromium.device.nfc.mojom.Nfc;
 import org.chromium.device.vibration.VibrationManagerImpl;
+import org.chromium.installedapp.mojom.InstalledAppProvider;
 import org.chromium.media.mojom.AndroidOverlayProvider;
 import org.chromium.mojo.system.impl.CoreImpl;
 import org.chromium.services.service_manager.InterfaceRegistry;
 import org.chromium.shape_detection.mojom.FaceDetectionProvider;
 
 @JNINamespace("content")
 class InterfaceRegistrarImpl {
 
     private static boolean sHasRegisteredRegistrars;
 
@@ skipping 24 matching lines @@
                 CoreImpl.getInstance().acquireNativeHandle(nativeHandle).toMessagePipeHandle());
         InterfaceRegistrar.Registry.applyRenderFrameHostRegistrars(registry, renderFrameHost);
     }
 
     private static void ensureContentRegistrarsAreRegistered() {
         if (sHasRegisteredRegistrars) return;
         sHasRegisteredRegistrars = true;
         InterfaceRegistrar.Registry.addContextRegistrar(new ContentContextInterfaceRegistrar());
         InterfaceRegistrar.Registry.addWebContentsRegistrar(
                 new ContentWebContentsInterfaceRegistrar());
+        InterfaceRegistrar.Registry.addRenderFrameHostRegistrar(
+                new ContentRenderFrameHostInterfaceRegistrar());
     }
 
     private static class ContentContextInterfaceRegistrar implements InterfaceRegistrar<Context> {
         @Override
         public void registerInterfaces(
                 InterfaceRegistry registry, final Context applicationContext) {
             registry.addInterface(
                     VibrationManager.MANAGER, new VibrationManagerImpl.Factory(applicationContext));
             registry.addInterface(
                     BatteryMonitor.MANAGER, new BatteryMonitorFactory(applicationContext));
             registry.addInterface(FaceDetectionProvider.MANAGER,
                     new FaceDetectionProviderImpl.Factory(applicationContext));
             registry.addInterface(AndroidOverlayProvider.MANAGER,
                     new AndroidOverlayProviderImpl.Factory(applicationContext));
             // TODO(avayvod): Register the PresentationService implementation here.
         }
     }
 
     private static class ContentWebContentsInterfaceRegistrar
             implements InterfaceRegistrar<WebContents> {
         @Override
         public void registerInterfaces(InterfaceRegistry registry, final WebContents webContents) {
             registry.addInterface(Nfc.MANAGER, new NfcFactory(webContents));
         }
     }
+
+    private static class ContentRenderFrameHostInterfaceRegistrar

[dcheng, 2017/03/21 07:37:50]

Nit: though this CL didn't introduce it, it would be useful to have some
comments describing the difference between ContentContextInterfaceRegistrar,
ContentWebContentsInterfaceRegistrar, and
ContentRenderFrameHostInterfaceRegistrar. I don't actually know what the
difference is at all, and it's not clear why there are 3 different types of
registrations.

[Matt Giuca, 2017/03/21 07:46:01]

The 3 different types are just for clients that require different arguments. For
example, I originally only needed an ApplicationContext so I was registering in
ContentContextInterfaceRegistrar, but then I realised I needed the RFH so I
moved it here.

I can add comments, but this really should be done in a separate CL because
there are a number of similar files to this (one in chrome/ for example) and it
doesn't make sense to be commenting those other files in this same (already
gigantic) CL.

[dcheng, 2017/03/22 01:23:26]

Sure, followup CL is fine. It's just hard for a non-Java person to understand
what the difference is between these (especially ContextRegistrar) and if there
are lifetime differences.

+            implements InterfaceRegistrar<RenderFrameHost> {
+        @Override
+        public void registerInterfaces(
+                InterfaceRegistry registry, final RenderFrameHost renderFrameHost) {
+            registry.addInterface(
+                    InstalledAppProvider.MANAGER, new InstalledAppProviderFactory(renderFrameHost));
+        }
+    }
 }