1116113 - Developer edition/Browser Console: Turning off Javascript Log hides uncaught exceptions by addon code.

Status: RESOLVED INVALID

(DevTools :: Console, defect)

Description

[Naja Melan]

The browser console has three warning levels for JavaScript (Error, Warning and Log) Somehow all warnings (uncaught exceptions) from addon (or all chrome?) code end up in the log section, making it impossible to see errors without a lot of noise (debug and info messages).

The problem also affects the addon debugger, since that only provides Error and Warning, which means that exceptions in the addon being debugged don't show up at all. That's not very good for debugging.

Also I have the impression that log messages aren't parsed the same way, so call stack traces are output with no formatting whatsoever which makes them very unreadable: 

1419852990126	addons.xpi	WARN	Exception running bootstrap method startup on [e-mail]: TypeError: browser.document is undefined (chrome://addon/content/Someclass.js:193:3) JS Stack trace: [e-mail]:193:4 < [e-mail]:60:3 < [e-mail]:51:3 < startup@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///xxx/.mozilla/firefox/qsdfmlkm.dev-edition-default/extensions/[e-mail]:14:22 < [e-mail]:4436:9 < AI_startInstall/<@XPIProvider.jsm:5820:13 < [e-mail]:330:41 < [e-mail]:870:23 < [e-mail]:749:7 < this.PromiseWalker.scheduleWalkerLoop/<@Promise-backend.js:691:37

Btw, I would have stressed my 3G connection to download a nightly build, but neither of these provides that:

https://nightly.mozilla.org/
https://developer.mozilla.org/en-US/Firefox/Developer_Edition

Comment 1

[Naja Melan]

Some more issues with the Console:

It doesn't seem to word wrap at the screen width, so I always have to scroll to the right quite far to see the file:linenumber that caused the console entry.

Another thing that is handier in the error console is that you can right click/copy for the whole entry, whereas for the consoles you can only copy text that you have selected. This might be by design, but it seems better to allow copying everything especially if the user selects copy while having selected nothing.

Comment 2

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(In reply to Naja Melan from comment #1)
> Some more issues with the Console:
> 
> It doesn't seem to word wrap at the screen width, so I always have to scroll
> to the right quite far to see the file:linenumber that caused the console
> entry.
> 
> Another thing that is handier in the error console is that you can right
> click/copy for the whole entry, whereas for the consoles you can only copy
> text that you have selected. This might be by design, but it seems better to
> allow copying everything especially if the user selects copy while having
> selected nothing.

Once again, please file new bugs for separate issues.  It is not helpful to lump a bunch of unrelated issues into one bug.

Comment 3

[Naja Melan]

ok, I'll file two more issues for this but then I have to get back to work really.

Comment 4

[DarkAngelBA]

When I installed the "developer edition" the javascript errors appears as a small red baloon on the bottom, one day I click on the "x" and it goes forever..
The only way to debug javascript is opening the browser console (in a separate window)
After googling a lot, and a few hacks, can't find a way to get it back.

Comment 5

[DarkAngelBA]

(In reply to DarkAngelBA from comment #4)
> When I installed the "developer edition" the javascript errors appears as a
> small red baloon on the bottom, one day I click on the "x" and it goes
> forever..
> The only way to debug javascript is opening the browser console (in a
> separate window)
> After googling a lot, and a few hacks, can't find a way to get it back.

--> It happened just after the Multithread Beta!! has the same "issue" with firebug

Comment 6

[Nicolas Chevobbe [:nchevobbe]]

We don't have such levels anymore.