[Android] Use resource throttle instead of HandleExternalProtocol.

chrome/browser/ui/android/external_protocol_dialog_android.cc

Index: chrome/browser/ui/android/external_protocol_dialog_android.cc
diff --git a/chrome/browser/ui/android/external_protocol_dialog_android.cc b/chrome/browser/ui/android/external_protocol_dialog_android.cc
index a39764e22f1bf8c6729efe8519fdb229cdfef24f..dc9bb6b59c2fa251245db98595abf4411a9d0bd8 100644
--- a/chrome/browser/ui/android/external_protocol_dialog_android.cc
+++ b/chrome/browser/ui/android/external_protocol_dialog_android.cc
@@ -13,11 +13,8 @@ using content::WebContents;
 // static
 void ExternalProtocolHandler::RunExternalProtocolDialog(
     const GURL& url, int render_process_host_id, int routing_id) {
-  WebContents* web_contents = tab_util::GetWebContentsByID(
-      render_process_host_id, routing_id);
-  if (web_contents) {
-    TabAndroid* tab = TabAndroid::FromWebContents(web_contents);
-    if (tab)
-      return tab->RunExternalProtocolDialog(url);
-  }
+  // Chrome on Android uses a throttle-based mechansim to intercept links
+  // so that the user may choose to run an Android application instead of
+  // loading the link in the browser. This mechanism also handles external
+  // protocols, so we don't need to do anything here.

[mkosiba (inactive), 2012/10/25 09:02:12]

NOTREACHED?

[John Knottenbelt, 2012/10/25 16:17:27]

Done.

 }