Extension Error Piping - Blink: WebKit Side

Source/WebKit/chromium/src/ChromeClientImpl.h

Index: Source/WebKit/chromium/src/ChromeClientImpl.h
diff --git a/Source/WebKit/chromium/src/ChromeClientImpl.h b/Source/WebKit/chromium/src/ChromeClientImpl.h
index 7f12b918c8b4d94c9cee37dd877c75e921359308..297597f3d0d4e857317ffd959861d7fa5a9d1cc3 100644
--- a/Source/WebKit/chromium/src/ChromeClientImpl.h
+++ b/Source/WebKit/chromium/src/ChromeClientImpl.h
@@ -98,6 +98,10 @@ public:
         WebCore::MessageSource, WebCore::MessageLevel,
         const WTF::String& message, unsigned lineNumber,
         const WTF::String& sourceID);
+    virtual bool shouldReportDetailedMessage(const WTF::String& source);
+    virtual void reportDetailedMessage(const WTF::String& source,
+        WebCore::MessageLevel, const WTF::String& message,
+        const WTF::String& jsonStackTrace);

[Matt Perry, 2013/07/10 23:32:07]

I think it would be better to extend addMessageToConsole to include the optional
stack trace.

[Devlin, 2013/07/11 01:15:44]

Yeah, how much to merge addMessageToConsole() (and related) was my biggest
question.  Should we still keep didAddMessageToConsole() and 
reportDetailedMessage() separate (and just merge in addMessageToConsole()),
d'you think?

[Matt Perry, 2013/07/11 02:40:46]

Yeah, I'd combine them all. This doesn't feel like a separate event - it's just
extra data on the addMessageToConsole event.

     virtual bool canRunBeforeUnloadConfirmPanel();
     virtual bool runBeforeUnloadConfirmPanel(
         const WTF::String& message, WebCore::Frame*);