Add some useful Chrome URLs to chrome://chrome-urls/.

chrome/browser/browser_about_handler.cc

Index: chrome/browser/browser_about_handler.cc
diff --git a/chrome/browser/browser_about_handler.cc b/chrome/browser/browser_about_handler.cc
index 580559953cf18050adf450c563674bd8c01921be..73df3e66d79448bd926397d72e4eb9f51a9ba9c2 100644
--- a/chrome/browser/browser_about_handler.cc
+++ b/chrome/browser/browser_about_handler.cc
@@ -109,24 +109,36 @@ namespace {
 const char* const kChromePaths[] = {
   chrome::kChromeUIAppCacheInternalsHost,
   chrome::kChromeUIBlobInternalsHost,
+  chrome::kChromeUIBookmarksHost,
+  chrome::kChromeUICacheHost,
   chrome::kChromeUIChromeURLsHost,
   chrome::kChromeUICrashesHost,
   chrome::kChromeUICreditsHost,
   chrome::kChromeUIDNSHost,
+  chrome::kChromeUIDownloadsHost,
+  chrome::kChromeUIExtensionsHost,
   chrome::kChromeUIFlagsHost,
   chrome::kChromeUIFlashHost,
-  chrome::kChromeUIGpuInternalsHost,

[Peter Kasting, 2011/07/12 23:37:28]

Are these two "internals" URLs deprecated versions of the "non-internals"
versions you've included?

[msw, 2011/07/13 00:11:08]

Hmm, I guess the internals URLs are meant to supersede their non-internals
counterparts (looking at crrev.com/71435 and crrev.com/69211). The two pairs
navigate to the same new DOMUI pages, but I'll revert to the internals URLs,
since "-internals" seems intentional for whatever reason.

+  chrome::kChromeUIGpuHost,
   chrome::kChromeUIHistogramsHost,
+  chrome::kChromeUIHistoryHost,
+  chrome::kChromeUIIPCHost,
   chrome::kChromeUIMemoryHost,
   chrome::kChromeUINetInternalsHost,
   chrome::kChromeUINetworkViewCacheHost,
+  chrome::kChromeUINewTabHost,
   chrome::kChromeUIPluginsHost,
+  chrome::kChromeUIPrintHost,
+  chrome::kChromeUIQuotaInternalsHost,
+  chrome::kChromeUISessionsHost,
   chrome::kChromeUISettingsHost,
   chrome::kChromeUIStatsHost,
-  chrome::kChromeUISyncInternalsHost,
+  chrome::kChromeUISyncHost,
+  chrome::kChromeUITasksHost,
   chrome::kChromeUITCMallocHost,
   chrome::kChromeUITermsHost,
   chrome::kChromeUIVersionHost,
+  chrome::kChromeUIWorkersHost,
 #ifdef TRACK_ALL_TASK_OBJECTS
   chrome::kChromeUITasksHost,
 #endif
@@ -134,12 +146,21 @@ const char* const kChromePaths[] = {
   chrome::kChromeUIConflictsHost,
 #endif
 #if defined(OS_LINUX)
+  chrome::kChromeUILinuxProxyConfigHost,
   chrome::kChromeUISandboxHost,
 #endif
 #if defined(OS_CHROMEOS)
-  chrome::kChromeUINetworkHost,
+  chrome::kChromeUIActiveDownloadsHost,
+  chrome::kChromeUIChooseMobileNetworkHost,
   chrome::kChromeUICryptohomeHost,
+  chrome::kChromeUIImageBurnerHost,
+  chrome::kChromeUIKeyboardOverlayHost,
+  chrome::kChromeUILoginHost,
+  chrome::kChromeUINetworkHost,
+  chrome::kChromeUIOobeHost,
   chrome::kChromeUIOSCreditsHost,
+  chrome::kChromeUIProxySettingsHost,
+  chrome::kChromeUISystemInfoHost,
 #endif
 };
 
@@ -394,6 +415,8 @@ std::string ChromeURLs() {
   AppendHeader(&html, 0, "Chrome URLs");
   AppendBody(&html);
   html += "<h2>List of Chrome URLs</h2>\n<ul>\n";
+  std::string about_blank(chrome::kAboutBlankURL);
+  html += "<li><a href='" + about_blank + "/'>" + about_blank + "</a></li>\n";

[Peter Kasting, 2011/07/12 23:37:28]

I don't think about:blank is that useful, it just looked odd that we had about:
URLs and it wasn't listed.

Now that the URLs are all chrome:// URLs, I think it's fine (and looks less
weird) to just leave it out.

[msw, 2011/07/13 00:11:08]

Done.

   std::vector<std::string> paths(ChromePaths());
   for (std::vector<std::string>::const_iterator i = paths.begin();
        i != paths.end(); ++i)