Display DNS probe results.

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index df8ab6e39f542624aa4382688db828a117f4822f..d982440472456114bf16286c3d1a22d69a34c76f 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -9452,6 +9452,13 @@ The following plug-in is unresponsive: <ph name="PLUGIN_NAME">$1
         <ph name="PRODUCT_NAME">&lt;span jscontent="productName"&gt;&lt;/span&gt;<ex>Google Chrome</ex></ph>
         won't use insecure connections in order to protect your privacy.
       </message>
+      <message name="IDS_ERRORPAGES_SUMMARY_DNS_PROBE_RUNNING" desc="Summary in the error page when DNS resolution failed and we are running a probe to figure out why.">
+        The server at
+        <ph name="HOST_NAME">&lt;strong jscontent="hostName"&gt;&lt;/strong&gt;<ex>www.whatever.com</ex></ph>
+        can't be found, because the DNS lookup failed.  Please hold on a moment while 

[mmenke, 2013/04/10 16:56:58]

Maybe "DNS" -> "host name"?  Less technical for the average user.

[Deprecated (see juliatuttle), 2013/04/10 23:42:32]

Done.

+        <ph name="PRODUCT_NAME">&lt;span jscontent="productName"&gt;&lt;/span&gt;<ex>Google Chrome</ex></ph>

[mmenke, 2013/04/10 16:56:58]

Substituting the product name in strings like this is now considered a bad idea,
since nouns change form depending on usage in some languages.  Instead, we
either shouldn't use the product name, or have two copies of the string, with
the name inlined - one each in chromium_resources.grd and
google_chrome_resouces.grd (I may have the file names wrong - they're in the
same directory as generated_resources.grd).

[Deprecated (see juliatuttle), 2013/04/10 23:42:32]

Done.

+        tries to figure out what's causing this problem.
+      </message>
 
       <message name="IDS_ERRORPAGES_ERROR_CODE" desc="At the bottom of error pages, a non-internationalized string or numeric code is displayed for debugging purposes">
         Error code: <ph name="ERROR_NAME">$1<ex>ERR_FILE_NOT_FOUND</ex></ph>
@@ -9523,6 +9530,9 @@ The following plug-in is unresponsive: <ph name="PLUGIN_NAME">$1
         Multiple distinct Location headers received.  This is disallowed to protect
         against HTTP response splitting attacks.
       </message>
+      <message name="IDS_ERRORPAGES_DETAILS_DNS_PROBE_RUNNING" desc="The error message displayed when we are waiting to see whether we will run a DNS probe.">
+        Waiting for DNS probe.
+      </message>

[mmenke, 2013/04/10 16:56:58]

Something to think about:  May make sense just to use the ERR_NAME_NOT_RESOLVED
string here in all cases, to reduce flicker.

[Deprecated (see juliatuttle), 2013/04/10 23:42:32]

I'm okay with a tiny grey message flickering, and I want the info there if, say,
the prober breaks and never returns results, so users can report that it's stuck
in this state.

       <message name="IDS_ERRORPAGES_DETAILS_UNKNOWN" desc="The default error message displayed if we don't have a more specific error message.">
         Unknown error.
       </message>