Make import failures log errors

sky/engine/core/frame/FrameConsole.cpp

Index: sky/engine/core/frame/FrameConsole.cpp
diff --git a/sky/engine/core/frame/FrameConsole.cpp b/sky/engine/core/frame/FrameConsole.cpp
index f619702a7c7e3c614787a7bf218af1f1ef0d92d8..ce351e577b35001b25df84b9bcba314c4e7a8ded 100644
--- a/sky/engine/core/frame/FrameConsole.cpp
+++ b/sky/engine/core/frame/FrameConsole.cpp
@@ -96,9 +96,6 @@ void FrameConsole::addMessage(PassRefPtr<ConsoleMessage> prpConsoleMessage)
 
     messageStorage()->reportMessage(consoleMessage);
 
-    if (consoleMessage->source() == CSSMessageSource || consoleMessage->source() == NetworkMessageSource)

[eseidel, 2014/11/06 23:08:52]

Why did you need to remove this?

[rafaelw, 2014/11/06 23:10:45]

Loggin to stddout happens the call below to .chromeClient().addMessageToConsole.
I suspect that DevTools uses the messageStorage() above.

On 2014/11/06 23:08:52, eseidel wrote:

[rafaelw, 2014/11/06 23:14:11]

Note: I didn't fully follow the path that Blink/Devtools takes. In blink, import
failures do long to the console (as well as the network tab) despite this return
for CSS & Network types - which made me assure they were arriving their somehow
via the messageStorage.

-        return;
-
     RefPtr<ScriptCallStack> reportedCallStack = nullptr;
     if (consoleMessage->source() != ConsoleAPIMessageSource) {
         if (consoleMessage->callStack() && m_frame.chromeClient().shouldReportDetailedMessageForSource(messageURL))