Extended Error Console for Pale Moon 27+

[shf84]

Hi, I'am an extension developer and since Pale Moon ver.27 some of my extension's functions work not properly. Trying to debug the extension with the "console.log()" statements, I found out that the Browser Console window is no longer available. I've installed the Developer Tools extension and the OP's extension Error Console but they do not show me messages from my extension code like the Browser Console did. Could anyone point me how am I supposed to debug my extension and fix it without the Browser Console window? Thanks in advance!

[ketmar]

there is nothing very special in that "console" object, it is just a wrapper for system console interface:

Code: Select all

const conService = Cc["@mozilla.org/consoleservice;1"].getService(Ci.nsIConsoleService);
function conlog (str) conService.logStringMessage(str);

[JustOff]

You could also try Components.utils.reportError or dump.

[win7-7]

Hi, I'am an extension developer and since Pale Moon ver.27 some of my extension's functions work not properly. Trying to debug the extension with the "console.log()" statements, I found out that the Browser Console window is no longer available. I've installed the Developer Tools extension and the OP's extension Error Console but they do not show me messages from my extension code like the Browser Console did. Could anyone point me how am I supposed to debug my extension and fix it without the Browser Console window? Thanks in advance!

Or if you want Mozilla devtools be available in Pale Moon you could compile Pale Moon from source with Mozilla devtools enabled in .mozconfig?

I compile from source personally with devtools enabled as I want Mozilla devtools.

[0strodamus]

Would you mind listing the exact .mozconfig options you used to enable the devtools, ie "ac_add_options --enable-devtools"?

[trava90]

Would you mind listing the exact .mozconfig options you used to enable the devtools, ie "ac_add_options --enable-devtools"?

That is the correct mozconfig option.

[0strodamus]

Thanks trava90!

[thosrtanner]

I am moderately confused by this thread because under my tools/web developer menu there is 'browser console'. And it works fine. So which browser console is it that is no longer there?

[Moonchild]

I am moderately confused by this thread because under my tools/web developer menu there is 'browser console'. And it works fine. So which browser console is it that is no longer there?

This is no longer relevant since we reintroduced and fixed up the devtools, as well as having the toolkit error console available.

[thosrtanner]

I am moderately confused by this thread because under my tools/web developer menu there is 'browser console'. And it works fine. So which browser console is it that is no longer there?

This is no longer relevant since we reintroduced and fixed up the devtools, as well as having the toolkit error console available.

Oh, right. Thanks

[Lootyhoof]

I am moderately confused by this thread because under my tools/web developer menu there is 'browser console'. And it works fine. So which browser console is it that is no longer there?

This is no longer relevant since we reintroduced and fixed up the devtools, as well as having the toolkit error console available.

This is the support thread for Error Console², an extension that does still work and its intended purpose is to provide more information than the standard Toolkit error console, which it does do (in my experience, at least). It's only as relevant as the Toolkit error console is.

As for whether people should use the browser console or the Toolkit error console (either with or without Error Console²), that is mostly up to personal preference, I'd say.

[Moonchild]

Sorry if I caused confusion here - I just meant to say that the initial posts in this thread are no longer relevant (it having started out as a necessity for not having devtools in the browser in initial releases of pale Moon 27).