Show alert failure for reloading unpacked extensions with bad manifest

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 e81f342514a2e9ab4f8cc1315a19bb45e36f8712..e6851e81ef54c070bae302b21a8e47a5808289dd 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -4777,6 +4777,9 @@ Make sure you do not expose any sensitive information.
         <message name="IDS_EXTENSIONS_LOAD_COULD_NOT_LOAD_MANIFEST" desc="The text to indicate that the source of the extension's manifest failed to load.">
           Could not load manifest.
         </message>
+        <message name="IDS_EXTENSIONS_LOAD_ADDITIONAL_FAILURES" desc="The text displayed above additional extension load failures.">
+          Additional failures:

[Finnur, 2014/07/15 10:38:45]

The problem I have with this label is that it lacks sufficient clarity. When I
looked at the screenshot you provided: http://i.imgur.com/02tzoUK.png, the first
thing I thought was "Additional failures" is listing other problems it found
with Invalid3. But that's not what was intended.

I would suggest removing the ambiguity and use a string such as:
Other extensions failing to load:

What do you think?

I'm actually also tempted to change IDS_EXTENSIONS_LOAD_ERROR_HEADING to:
Error loading extension
("Extension Load Error" sounds a bit dry)

[Devlin, 2014/07/15 17:51:44]

These both SGTM.

[gpdavis, 2014/07/15 18:33:14]

Ah, I see where the confusion came from.  That sounds reasonable to me.  I'll go
ahead and update these.

+        </message>
         <message name="IDS_EXTENSIONS_ERRORS_SHOW_MORE" desc="The text which allows the user to display more errors for a given extension.">
           Show more...
         </message>