Expose the MacViewsWebUIDialogs feature flag to chrome://flags

chrome/browser/ui/browser_dialogs_mac.cc

 // Copyright 2015 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.
 
 #include "chrome/browser/ui/browser_dialogs.h"
 
 #include "base/command_line.h"
 #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);
 }
 
 bool ToolkitViewsWebUIDialogsEnabled() {
   return base::FeatureList::IsEnabled(kMacViewsWebUIDialogs);
 }
 
 }  // namespace chrome