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

chrome/browser/ui/views/external_protocol_dialog.cc

Index: chrome/browser/ui/views/external_protocol_dialog.cc
diff --git a/chrome/browser/ui/views/external_protocol_dialog.cc b/chrome/browser/ui/views/external_protocol_dialog.cc
index 1cfc6c81bc2e221940b17399f9486d9d55ab15a2..1feeb32b83fba8c287eb277abca2e57f55223c07 100644
--- a/chrome/browser/ui/views/external_protocol_dialog.cc
+++ b/chrome/browser/ui/views/external_protocol_dialog.cc
@@ -15,6 +15,7 @@
 #include "components/constrained_window/constrained_window_views.h"
 #include "content/public/browser/web_contents.h"
 #include "ui/base/l10n/l10n_util.h"
+#include "ui/base/ui_features.h"
 #include "ui/gfx/text_elider.h"
 #include "ui/views/controls/message_box_view.h"
 #include "ui/views/widget/widget.h"
@@ -30,6 +31,9 @@ const int kMessageWidth = 400;
 ///////////////////////////////////////////////////////////////////////////////
 // ExternalProtocolHandler
 
+#if !defined(OS_MACOSX) || BUILDFLAG(MAC_VIEWS_BROWSER)
+// This should be kept in sync with RunExternalProtocolDialogViews in

[msw, 2017/01/24 08:39:37]

It'd be nice to avoid this duplication, is it tough to avoid that?

[karandeepb, 2017/01/24 08:43:57]

It isn't actually. The rationale for this is that we want to restrict most of
the changes to chrome/browser/ui/cocoa so as to minimize the changes we need to
undo once we switch fully to MacViews.

+// external_protocol_dialog_views_mac.mm.
 // static
 void ExternalProtocolHandler::RunExternalProtocolDialog(
     const GURL& url, int render_process_host_id, int routing_id,
@@ -46,6 +50,7 @@ void ExternalProtocolHandler::RunExternalProtocolDialog(
   new ExternalProtocolDialog(std::move(delegate), render_process_host_id,
                              routing_id);
 }
+#endif  // !OS_MACOSX || MAC_VIEWS_BROWSER
 
 ///////////////////////////////////////////////////////////////////////////////
 // ExternalProtocolDialog