Closed Bug 670583 Opened 14 years ago Closed 13 years ago

Missing Javascript Exceptions since FF4

Categories

(DevTools :: General, defect)

5 Branch
All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bugzilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0 Build ID: 20110615151330 Steps to reproduce: While writing an plugin, the plugin has a failure of some kind though no error is shown in the JS console, no exception is shown. Actual results: Nothing shows up in JS Console Expected results: Error should be reported in the console. I can confirm this is the case by wrapping the failing block of code in a try/catch and the exception is caught there. Most posts on the web point to: http://kb.mozillazine.org/Dom.report_all_js_exceptions which, among other things I have tried, they do not seem to fix the issue. I will attempt to post a smaller test case later this week, has anyone else reported anything similar? I did not find an open bug in the database about this.
This may be related to errors thrown from scripts loaded with .loadSubScript() and/or Components.utils.import(). The code I'm working in particular at the moment is using .loadSubScript() but I have seen this same thing occur with .import() as well in a similar/same context.
Hi Clint, Let's wait for your testcase then. Once uploaded, i'll take a look and perhaps we can confirm this. Thanks!
Hello Clint! Thanks for your bug report. Are you testing this with the Web Console or with the Error Console? Script errors from extensions are expected to show only in the Error Console. Please let us know what's the case, so we can proceed further with fixing this bug. Thank you!
and there was no more data.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Yeah, this is invalid, I'm not sure what I was running into at the time any more, but I'm clearly getting them now.
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.