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

chrome/browser/browser_resources.grd

Index: chrome/browser/browser_resources.grd
diff --git a/chrome/browser/browser_resources.grd b/chrome/browser/browser_resources.grd
index 6c919552623176a758e9485f0dd4b1d4752384fa..972afd785966da025aeaa7f0d0dd672bb1283528 100644
--- a/chrome/browser/browser_resources.grd
+++ b/chrome/browser/browser_resources.grd
@@ -30,7 +30,7 @@
       <include name="IDR_ABOUT_VERSION_HTML" file="resources\about_version.html" flattenhtml="true" allowexternalscript="true" type="BINDATA" />
       <include name="IDR_ABOUT_VERSION_JS" file="resources\about_version.js" type="BINDATA" />
       <include name="IDR_BOOKMARKS_MANIFEST" file="resources\bookmark_manager\manifest.json" type="BINDATA" />
-      <if expr="pp_if('webui_dialogs')">
+      <if expr="is_posix and not is_macosx">

[arv (Not doing code reviews), 2011/08/25 16:40:41]

Is it intentional that both CrOS and Linux gets these?

What about Android? It is posix too isn't it?

[flackr, 2011/08/25 20:40:47]

Just to address this question, it is intentional. As long as the
certificate_model functions are supported it shouldn't hurt to have the webui
certificate viewer compiled in. The logic matches that of chrome_common.gypi. Of
course let me know if you think this could be a problem. The main issue was
avoiding including the certificate viewer on windows and mac where because they
used a native certificate viewer the certificate_model functions were not
defined and it would fail in linking.

         <include name="IDR_CERTIFICATE_VIEWER_HTML" file="resources\certificate_viewer.html" type="BINDATA" />
         <include name="IDR_CERTIFICATE_VIEWER_JS" file="resources\certificate_viewer.js" type="BINDATA" />
         <include name="IDR_CERTIFICATE_VIEWER_CSS" file="resources\certificate_viewer.css" type="BINDATA" />