Extension Error Piping - Blink: Chrome Side

chrome/renderer/chrome_content_renderer_client.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/renderer/chrome_content_renderer_client.h"
 
 #include "base/command_line.h"
 #include "base/logging.h"
 #include "base/metrics/histogram.h"
 #include "base/path_service.h"
@@ skipping 1265 matching lines @@
   }
   // Allow access for tests.
   if (CommandLine::ForCurrentProcess()->HasSwitch(
           switches::kEnablePepperTesting)) {
     return true;
   }
 #endif  // !defined(OS_ANDROID)
   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