Bug 86015 - [Qt] Exceptions in JavaScript sources loading from the qrc:/ scheme do not contain a stacktrace object, nor an associated line number or description/message text
Summary: [Qt] Exceptions in JavaScript sources loading from the qrc:/ scheme do not co...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2012-05-09 13:58 PDT by Jarred Nicholls
Modified: 2014-02-03 03:20 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jarred Nicholls 2012-05-09 13:58:19 PDT
Firstly, I am not sure if this should be marked as a "WebCore JavaScript" component, but it is Qt specific obviously.

When a JavaScript source loaded from qrc:/ throws an exception, that exception object does not contain a stacktrace. Additionally the console error does not have an associated line number or exception message/description, instead showing a line number of 0 and a description of "undefined".

If a JS source is from any other remote (http://) or local (file://) origin, then the line number and exception message are accurately and readily available with the console error message.

qrc is of course recognized as a local scheme in WebCore, but perhaps JSC doesn't know what to do with qrc files in terms of providing exception information?
Comment 1 Jocelyn Turcotte 2014-02-03 03:20:48 PST
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.