Move Android to use new Popup Blocker API.

chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc

Index: chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc
diff --git a/chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc b/chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc
index 0d27929e56b6780ae2ffa1312fe7f78aeb8b8ba1..407557f9f0d896e47e10cad851109ee08afa1e33 100644
--- a/chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc
+++ b/chrome/browser/ui/blocked_content/popup_blocker_tab_helper.cc
@@ -20,6 +20,10 @@
 #include "content/public/browser/web_contents_view.h"
 #include "third_party/WebKit/public/web/WebWindowFeatures.h"
 
+#if defined(OS_ANDROID)
+#include "chrome/browser/ui/android/tab_model/tab_model_list.h"
+#endif
+
 using WebKit::WebWindowFeatures;
 
 DEFINE_WEB_CONTENTS_USER_DATA_KEY(PopupBlockerTabHelper);
@@ -139,7 +143,11 @@ void PopupBlockerTabHelper::ShowBlockedPopup(int32 id) {
   BlockedRequest* popup = blocked_popups_.Lookup(id);
   if (!popup)
     return;
+#if defined(OS_ANDROID)
+  TabModelList::HandleNavigation(&popup->params);

[Yaron, 2013/08/21 19:07:58]

So maybe this is how you can clean up the browser_navigator.cc dependency. You
could have android also implement chrome::Navigate with a different cc-file and
avoid introducing depending on browser_navigator.cc

[David Trainor- moved to gerrit, 2013/08/21 20:21:27]

To do that I'd have to pull apart browser_navigator.cc as right now
NavigateParams are in there along with these methods.  I can do that but I'd
rather do that in another CL.  Also chrome::Navigate does a LOT of stuff. 
Having a general case implementation will require more work.

+#else
   chrome::Navigate(&popup->params);
+#endif
   if (popup->params.target_contents) {
     popup->params.target_contents->Send(new ChromeViewMsg_SetWindowFeatures(
         popup->params.target_contents->GetRoutingID(), popup->window_features));