Steve Fenton

JavaScript Only Works When Firebug is Open

Please Note: If you are using a recent version of Firefox (i.e. it is 2014, not 2011 any more) you’ll notice that the console is always present – so you’ll never see this problem in Firefox again!

I can see this turning into one of those staple trick-questions at interviews, because this is a genuinely interesting problem and many people get quite medieval about it.

The issue is that you have a web page with some kind of problem. There is a JavaScript error somewhere and you need to track it down. So you open up Firebug or some other debugging tool and run the code – but you don’t get any errors and everything magically starts working.

The more superstitious amongst us will point out that some errors only happen when you aren’t watching and suggest sprinkling salt on your keyboard and maybe even blood letting.

The less dramatic amongst us will look for a tangible reason for the problem.

And here it is. This is exactly the kind of line that will cause exactly this kind of behaviour:

console.log("Some message for the console.");

So what’s the gotcha with this line of code? When you open Firebug, there is a console. When you close Firebug, there isn’t. Almost certainly, you wouldn’t expect there to be a console available in your live implementation – so you shouldn’t assume there will be one!

You can perform a couple of fixes for this… You can wrap your console.log statements in a try-catch block.

try {
    console.log("Some message for the console.");
} catch (error) { }

You can detect whether the console feature exists.

if (typeof console !== 'undefined') {
    console.log("Some message for the console.");

You can even implement your own “silent console” – this example does nothing, but you could write to an HTML element when “log” is called, for example!

if (typeof console === 'undefined') {
    var console = {};
    console.log = function() {};
    // same with console.assert et al

Written by Steve Fenton on