I'm not exactly sure when it started happening, roughly the last week or so, but Chrome no longer seems to print my console.log statements. I've included a screenshot where on the console I type console.log('hello world'), and it simply prints undefined. This is occuring on my Mac, Chrome Version 29.0.1547.65. This exact same test on my Windows machine (Chrome version 29.01547.66 m) produces the output
hello world
undefined
I don't believe I have any filtering turned on or am doing anything differently than I was roughly a week ago. Thanks for any suggestions in advance.
I'm not exactly sure when it started happening, roughly the last week or so, but Chrome no longer seems to print my console.log statements. I've included a screenshot where on the console I type console.log('hello world'), and it simply prints undefined. This is occuring on my Mac, Chrome Version 29.0.1547.65. This exact same test on my Windows machine (Chrome version 29.01547.66 m) produces the output
hello world
undefined
I don't believe I have any filtering turned on or am doing anything differently than I was roughly a week ago. Thanks for any suggestions in advance.
Share Improve this question asked Sep 12, 2013 at 23:07 Bradley BossardBradley Bossard 2,5192 gold badges25 silver badges30 bronze badges 4- does this still happen? I have the same version, and I do get 'hello world' but also undefined after it – Leon Gaban Commented Sep 12, 2013 at 23:10
-
console.logreturnsundefined, it's normal behavior. – elclanrs Commented Sep 12, 2013 at 23:11 - It says I have to wait 10 minutes to accept, I will once I can! – Bradley Bossard Commented Sep 12, 2013 at 23:19
- ohh i didn't know that (that you have to wait some time to accept an answer).. thanks :) – Orlando Commented Sep 13, 2013 at 2:20
2 Answers
Reset to default 4click in the funnel and make sure you have Logging checked
In my case the problem was Firebug Lite, which I thought I wasn't using at the moment (it was collapsed).
Open Firebug Lite and check off "Override Console Object".
Then the native Chrome console will receive messages again, and Firebug's console won't (like it couldn't print on both at the same time; go figure).