Extension Error Piping - Blink: Chrome Side

chrome/renderer/chrome_content_renderer_client.cc

Index: chrome/renderer/chrome_content_renderer_client.cc
diff --git a/chrome/renderer/chrome_content_renderer_client.cc b/chrome/renderer/chrome_content_renderer_client.cc
index 7a68264fbab94d920725f2fd78e9ea5e7832adb4..864075c22936cf70cf3b90cb818e3c78262a45a6 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -1283,5 +1283,14 @@ bool ChromeContentRendererClient::AllowPepperMediaStreamAPI(
   return false;
 }
 
+bool ChromeContentRendererClient::ShouldReportDetailedMessage(
+    const GURL& url) const {
+  // Currently, we are only interested in anything caused by an extension.
+  // A source came from an extension if it is either directly from the
+  // extension's url (chrome-extension://), or if it did not come from a real
+  // url at all (as in the source being "event_bindings").

[Devlin, 2013/07/11 00:55:35]

Are there any other cases in which we know something came from an extension?  Or
in which the "!url.is_valid()" case will include something we don't want?

+  return !url.is_empty() &&
+         (!url.is_valid() || url.host() == extensions::kExtensionScheme);
+}
 
 }  // namespace chrome