Reputation: 5738
Which solution do you recommend, the second is simpler ( less code ), but there are drawbacks on using it ?
First: (Set a global debug flag)
// the first line of code
var debug = true;
try {
console.log
} catch(e) {
if(e) {
debug=false;
}
};
// Then later in the code
if(debug) {
console.log(something);
}
Second: override console.log
try {
console.log
} catch(e) {
if (e) {
console.log = function() {}
}
};
// And all you need to do in the code is
console.log(something);
Upvotes: 28
Views: 36063
Reputation: 923
I've faced a similar bug in my past, and I overcame it with the code below:
if(!window.console) {
var console = {
log : function(){},
warn : function(){},
error : function(){},
time : function(){},
timeEnd : function(){}
}
}
Upvotes: 1
Reputation: 789
window.console = window.console || {};
window.console.log = window.console.log || function() {};
Upvotes: 0
Reputation: 25165
EDIT: Andy's answer is way more elegant than the quick hack I've posted below.
I generally use this approach...
// prevent console errors on browsers without firebug
if (!window.console) {
window.console = {};
window.console.log = function(){};
}
Upvotes: 3
Reputation: 3475
The following will achieve what you are looking for:
window.console && console.log('foo');
Upvotes: 0
Reputation: 3441
I came across this post, which is similar to the other answers:
http://jennyandlih.com/resolved-logging-firebug-console-breaks-ie
Upvotes: 0
Reputation: 1058
Or, in coffeescript:
window.console ?=
log:-> #patch so console.log() never causes error even in IE.
Upvotes: 6
Reputation: 344685
Neither, but a variation of the second. Lose the try...catch
and check for existence of the console object properly:
if (typeof console == "undefined") {
window.console = {
log: function () {}
};
}
console.log("whatever");
Upvotes: 56