Expose the MacViewsWebUIDialogs feature flag to chrome://flags

chrome/browser/ui/browser_dialogs_mac.cc

Index: chrome/browser/ui/browser_dialogs_mac.cc
diff --git a/chrome/browser/ui/browser_dialogs_mac.cc b/chrome/browser/ui/browser_dialogs_mac.cc
index a85fbcbe6e1bd2a6d94dddf318f07415fde762fa..9ed5b834525dc14338178ee240fc212214b6022b 100644
--- a/chrome/browser/ui/browser_dialogs_mac.cc
+++ b/chrome/browser/ui/browser_dialogs_mac.cc
@@ -8,12 +8,12 @@
 #include "base/feature_list.h"
 #include "chrome/common/chrome_switches.h"
 
+namespace chrome {
+
 const base::Feature kMacViewsWebUIDialogs {
   "MacViewsWebUIDialogs", base::FEATURE_DISABLED_BY_DEFAULT
 };
 
-namespace chrome {
-
 bool ToolkitViewsDialogsEnabled() {
   return base::CommandLine::ForCurrentProcess()->HasSwitch(

[msw, 2016/05/24 17:01:29]

optional nit: convert this to a feature for parity?

[tapted, 2016/05/25 12:01:49]

Done. I do like consistency :). But my conscience wouldn't let me just tick the
commit box.. a couple of new files are in the diff now.

I guess it raises the issue of whether ToolkitViewsDialogsEnabled() should be
renamed too, but that's a bit more churn - a follow-up perhaps. But also if
things go smoothly, ToolkitViewsWebUIDialogsEnabled() goes away "soon" and
ToolkitViewsDialogsEnabled() makes sense again by itself, so maybe it's fine as
is.

       switches::kEnableMacViewsDialogs);