MacViews: Enable views based External Protocol dialog behind secondary-ui-md flag.

chrome/browser/ui/browser_dialogs.h

 // Copyright (c) 2012 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.
 
 #ifndef CHROME_BROWSER_UI_BROWSER_DIALOGS_H_
 #define CHROME_BROWSER_UI_BROWSER_DIALOGS_H_
 
 #include <string>
 #include <utility>
 #include <vector>
 
 #include "base/callback.h"
 #include "build/build_config.h"
 #include "chrome/browser/ui/bookmarks/bookmark_editor.h"
 #include "third_party/skia/include/core/SkColor.h"
+#include "ui/base/page_transition_types.h"
 #include "ui/gfx/native_widget_types.h"
 
 #if defined(OS_CHROMEOS)
 #include "chrome/browser/chromeos/arc/intent_helper/arc_navigation_throttle.h"
 #endif  // OS_CHROMEOS
 
 class Browser;
 class ContentSettingBubbleModel;
 class GURL;
 class LoginHandler;
@@ skipping 117 matching lines @@
 // Creates a toolkit-views based LoginHandler (e.g. HTTP-Auth dialog).
 LoginHandler* CreateLoginHandlerViews(net::AuthChallengeInfo* auth_info,
                                       net::URLRequest* request);
 
 // Shows the toolkit-views based BookmarkEditor.
 void ShowBookmarkEditorViews(gfx::NativeWindow parent_window,
                              Profile* profile,
                              const BookmarkEditor::EditDetails& details,
                              BookmarkEditor::Configuration configuration);
 
+// Shows the toolkit-views based External Protocol dialog.
+void RunExternalProtocolDialogViews(const GURL& url,

[tapted, 2017/01/17 21:17:13]

Does this need to be here, or can it be a data member of ExternalProtocolHandler
as well?

(maybe BUILDFLAG(MAC_VIEWS_BROWSER) will help do this now)

[karandeepb, 2017/01/19 03:59:43]

It can be a static member function. Don't think it should be public though,
since it's an implementation detail. Maybe a private static function. Although
this is similar to how we do this for other dialogs.

[tapted, 2017/01/20 05:53:52]

ExternalProtocolDialog currently uses static class functions - we should stick
with that

+                                    int render_process_host_id,
+                                    int routing_id,
+                                    ui::PageTransition page_transition,
+                                    bool has_user_gesture);
+
 void ShowPaymentRequestDialog(payments::PaymentRequest* request);
 
 #if defined(OS_MACOSX)
 
 // This is a class so that it can be friended from ContentSettingBubbleContents,
 // which allows it to call SetAnchorRect().
 class ContentSettingBubbleViewsBridge {
  public:
   static void Show(gfx::NativeView parent_view,
                    ContentSettingBubbleModel* model,
@@ skipping 24 matching lines @@
 using BubbleShowPtr =
     void (*)(content::WebContents*,
              const std::vector<arc::ArcNavigationThrottle::AppInfo>&,
              const IntentPickerResponse&);
 
 BubbleShowPtr ShowIntentPickerBubble();
 
 #endif  // OS_CHROMEOS
 
 #endif  // CHROME_BROWSER_UI_BROWSER_DIALOGS_H_