Changes to console.log behaviour in SDK 1.14

In 1.14 we added some additional features to the console API and also set the default log level to “error” instead of “info” for add-ons installed into Firefox via the Add-on Manager and Add-on Builder Helper as well as tools like the Extension Auto-installer.

An unfortunate side-effect is that by default, developers using these tools will no longer see messages from console.log() in the jsconsole window.

We have provided the ability for developers to set preferences to control logging behavior both globally and for a specific add-on, and by setting one of these preferences you can override the default.

I’m just wondering, several hours can’t figure out how to enable console.log into an extension content script? Firefox 22; SDK 1.4; extensions.sdk.console.logLevel set to true,
but nothing happens.

P.S How developers can develop great extensions (like on Chrome) for Firefox without console support?
Why they should configure Firefox and about:config several hours to start porting an extension?
Today’s this is just abnormal situation.

I added “extensions.sdk.console.logLevel”, and set the value to “all”, but I still can’t see console.log() messages from content scripts in the extension I’m working on. (Strangely, I also can’t see console.error() messages.) I followed your instructions, including restarting Firefox, and it is version 22. I’m stumped.

Additionally, I’m noticing that inserting “debugger;” calls in the content script doesn’t seem to bring up the debugger– how the heck are you supposed to debug content scripts?

What is driving me nuts is that it’s not consistent: I wish it didn’t work all the way.

It didn’t work, then I made it work for few days, and now it doesn’t anymore. I didn’t change the code (I was busy with other stuff). I’m a beginner (writing add-ons and JavaScript) and I’ll have not to rely on this.