Closed
Bug 1167086
Opened 9 years ago
Closed 5 years ago
Javascript exceptions from content with chrome privileges don't appear in the add-on console
Categories
(DevTools :: Console, defect)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: glandium, Unassigned)
Details
I was working on the js code for the tab stats addon (https://addons.mozilla.org/en-US/firefox/addon/tab-stats/) and broke it, which happens a lot considering how often I write javascript these days. Anyways, the addon ui is entirely in a web page with chrome privileges, so I was using the devtools, but I was completely lost because I wasn't seeing anything in the web console, so I used the debugger to go through the code and see the exception there, which was dreadful... until I realized the exceptions were in /a/ console... just not the web console, but the browser console. This may or may not be related to bug 802543.
Component: Developer Tools → Developer Tools: Console
Comment 1•9 years ago
|
||
Apart from the Browser Console & Browser Toolbox, we now have the Add-on Toolbox which you can get at from about:addons by clicking the "Debug" button. Doesn't that suffice or is it that you didn't know about these options?
Reporter | ||
Comment 2•9 years ago
|
||
I didn't know about it, but that doesn't help: the console there stays empty.
Comment 3•9 years ago
|
||
OK, that sounds like a bug in the Add-on Toolbox then (it may even be a dupe, but I can't find it right now). It is by design that the error doesn't appear in the web console.
Summary: Javascript exception from content with chrome privileges don't appear in the web console → Javascript exceptions from content with chrome privileges don't appear in the add-on console
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 4•5 years ago
|
||
I don't think this is an issue now that we have web extensions.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•