From afcac342082ab75dde6bb57e9ac1493f49ab7813 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Hugo=20Lindstr=C3=B6m?= <hugolm84@gmail.com>
Date: Wed, 12 Oct 2011 18:58:17 +0200
Subject: [PATCH] Dont allways assert on js failure

---
 src/libtomahawk/resolvers/qtscriptresolver.cpp | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/libtomahawk/resolvers/qtscriptresolver.cpp b/src/libtomahawk/resolvers/qtscriptresolver.cpp
index 6b3f4be07..bb7f1ec43 100644
--- a/src/libtomahawk/resolvers/qtscriptresolver.cpp
+++ b/src/libtomahawk/resolvers/qtscriptresolver.cpp
@@ -184,7 +184,11 @@ void
 ScriptEngine::javaScriptConsoleMessage( const QString& message, int lineNumber, const QString& sourceID )
 {
     tLog() << "JAVASCRIPT:" << m_scriptPath << message << lineNumber << sourceID;
-    Q_ASSERT( false );
+    /// I guess there is somereason for a assert in here, maybe fatal js errors, but
+    /// undefined is not so fatal
+    if(sourceID != "undefined")
+        Q_ASSERT( false );
+
 }