[Autofill]Enable mojo AutofillDriver for android_webview.

android_webview/browser/aw_content_browser_client.cc

Index: android_webview/browser/aw_content_browser_client.cc
diff --git a/android_webview/browser/aw_content_browser_client.cc b/android_webview/browser/aw_content_browser_client.cc
index 021681d964a9b368f0af0098405ebb5cd9e640f8..7c065fc45267aa99b3a95ea0ce9c7cfdf35c0a57 100644
--- a/android_webview/browser/aw_content_browser_client.cc
+++ b/android_webview/browser/aw_content_browser_client.cc
@@ -33,6 +33,7 @@
 #include "base/json/json_reader.h"
 #include "base/memory/ptr_util.h"
 #include "base/path_service.h"
+#include "components/autofill/content/browser/content_autofill_driver_factory.h"
 #include "components/cdm/browser/cdm_message_filter_android.h"
 #include "components/crash/content/browser/crash_micro_dump_manager_android.h"
 #include "components/navigation_interception/intercept_navigation_delegate.h"
@@ -55,6 +56,7 @@
 #include "net/android/network_library.h"
 #include "net/ssl/ssl_cert_request_info.h"
 #include "net/ssl/ssl_info.h"
+#include "services/service_manager/public/cpp/interface_registry.h"
 #include "ui/base/resource/resource_bundle.h"
 #include "ui/base/resource/resource_bundle_android.h"
 #include "ui/resources/grit/ui_resources.h"
@@ -539,4 +541,12 @@ AwContentBrowserClient::GetServiceManifestOverlay(const std::string& name) {
   return base::JSONReader::Read(manifest_contents);
 }
 
+void AwContentBrowserClient::RegisterRenderFrameMojoInterfaces(
+    service_manager::InterfaceRegistry* registry,
+    content::RenderFrameHost* render_frame_host) {
+  registry->AddInterface(
+      base::Bind(&autofill::ContentAutofillDriverFactory::BindAutofillDriver,

[vabr (Chromium), 2016/11/11 09:07:42]

When you bind this, does it mean that the browser-side will work the same in
WebView as it does in normal Chrome? In other words, would it be now left with
the renderer process to drop information it should not have access to?

[sgurun-gerrit only, 2016/11/18 23:51:28]

yes it works the same way as chrome. Specifically, when a form is seen, the
renderer sends a mojo message for forms seen:
https://cs.chromium.org/chromium/src/out/Debug/gen/components/autofill/conten...

which I think is the most important piece for webview.

[leonhsl(Using Gerrit), 2016/11/19 12:05:31]

Thanks sgurun@ a lot for the clarifications. As for the concern about renderer
process getting unnecessary information, I think:
  1, At least autofill mojo IPC is keeping the same logic with legacy chromium
IPC before, mojo is not making things worse. 
  2, It's true that chrome and webview have the same capability of sending
autofill mojo IPC messages, but, comparing the implementation of webview
autofill client with chrome autofill client, we can see that webview autofill
client is handling only those interested features, such as autocomplete, and is
ignoring others by empty or NOTIMPLEMENTED() functions, this means that actually
many mojo messages(except autocomplete) will never be triggered to be sent to
renderer process.

+                 render_frame_host));
+}
+
 }  // namespace android_webview