Closed Bug 526420 Opened 15 years ago Closed 14 years ago

Broken source links in error console

Categories

(Mozilla Labs :: Jetpack Prototype, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: adw, Unassigned)

Details

In errors and warnings in the error console, Jetpack shows source files as "chrome://jetpack/content/index.html -> foo.js", but when I click on those links, I get a blank view-source window and this error:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.loadURI]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://global/content/viewSource.js :: viewSource :: line 221"  data: no]

When I remove the "chrome://jetpack/content/index.html -> " prefix that's being inserted from JetpackRuntime.Context, clicking source links works as expected.

Atul, this makes it kind of a pain to debug errors.  Is there a reason that prefix is needed?  Can we work around this for 0.6?
We will be monitoring all these issues after the rebooted Jetpack code base is released in the first week of March to ensure their causes are not duplicated. Many of the bugs/issues with the prototype version of Jetpack will be made irrelevant given the structure of the new SDK.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.