Add --use-more-webui runtime flag to toggle WebUI replacements for native dialogs.

chrome/browser/browser_main.cc

Index: chrome/browser/browser_main.cc
diff --git a/chrome/browser/browser_main.cc b/chrome/browser/browser_main.cc
index d47d3ca72f2b256281ee42a88a168c1f6cf2880f..e23e35cc69d0ab832baf98de7f1d2cd9ac58d666 100644
--- a/chrome/browser/browser_main.cc
+++ b/chrome/browser/browser_main.cc
@@ -77,6 +77,7 @@
 #include "chrome/browser/ui/browser.h"
 #include "chrome/browser/ui/browser_init.h"
 #include "chrome/browser/ui/webui/chrome_url_data_manager_backend.h"
+#include "chrome/browser/ui/webui/chrome_web_ui.h"
 #include "chrome/browser/web_resource/gpu_blacklist_updater.h"
 #include "chrome/common/chrome_constants.h"
 #include "chrome/common/chrome_paths.h"
@@ -1497,9 +1498,16 @@ int BrowserMain(const MainFunctionParams& parameters) {
   RegisterTranslateableItems();
 #endif
 
+  ChromeWebUI::SetMoreWebUI(

[Rick Byers, 2011/08/18 19:25:30]

Rather that keep a separate flag which you set at startup, you could just have a
getter that computes the value on demand.  I'm not sure which approach is more
common, but that's what the NTP4 code does, see NewTabUI::NTP4Enabled().  This
startup function is long enough that avoiding adding any code to it might be
nice.  But again, assuming lookup is fast either way, I'd go with whichever
style is more common for runtime flags...

[flackr, 2011/08/23 17:41:44]

Done.

+      CommandLine::ForCurrentProcess()->HasSwitch(switches::kUseMoreWebUI));
+
 #if defined(TOOLKIT_VIEWS)
   views::Widget::SetPureViews(
       CommandLine::ForCurrentProcess()->HasSwitch(switches::kUsePureViews));
+  // If using Pure Views, turn on More WebUI to remove as much GTK as possible.
+  if (views::Widget::IsPureViews()) {
+    ChromeWebUI::SetMoreWebUI(true);
+  }
   // Launch the views desktop shell window and register it as the default parent
   // for all unparented views widgets.
   if (parsed_command_line.HasSwitch(switches::kViewsDesktop)) {