Reputation: 49659
I am logging using the jQuery.log plugin (which logs to console.log if available) and I am not seeing any of the logging messages appear in the Chrome JavaScript console.
Logging works on Firebug's console under Firefox, but I did have to explicitly enable the Firebug JavaScript console. Have a missed some option somewhere under Chrome?
Edit:
The only thing being logged to the console is
Uncaught Syntax error, unrecognized expression: |button
I assume that the Chrome console is suppose to log statements even after errors like the one above, but there may be some kind of issue with Chrome here, see http://code.google.com/p/chromium/issues/detail?id=29062. I am using Chrome 5.0.375 under Linux and that bug is listed as a Windows XP, Chrome 4.0 issue, it could still apply.
Upvotes: 43
Views: 106994
Reputation: 379
I have this error by have obfuscated javascript code, deobfuscate and console.log work again)
Upvotes: 0
Reputation: 86473
Make sure you have the console showing and that it is showing "All".
The cursor is on the button to hide/show the console.
Update: In newer versions of Chrome, you need to click the filter icon, then make sure "All" is selected.
Upvotes: 50
Reputation: 485
Resetting default setting works for me.
While in the console tab, pressingF1
should open the setting page. There you will different settings that you can adjust including the button Restore defaults and reload
.
Upvotes: 1
Reputation: 5289
For me, it was because the script was being cached and the browser was not loading my latest version.
Try Ctrl+F5
to reload your page.
Upvotes: 0
Reputation: 2664
On my computer I had accidently clicked the Debug filter. This made my log messages hidden. Here's how it was before (hidden messages):
Here's how it was after the change (working messages):
Upvotes: 5
Reputation: 973
When playing around with example Chrome Extensions, I was often unable to see the console.log messages when looking at console (ctrl+shift+j). But then I realized, that I was in the wrong place.
Wrench -> Tools -> Extensions and then click on the appropriate link under "Inspect active views". (in the Chrome examples it is often background.html) This should bring up the console that you are looking for.
Upvotes: 20
Reputation: 57
I am not sure if this is the case, but if you are using firebug with chrome, you have to turn firebug off in order for console.log() to work in Developer Tools.
Upvotes: 3
Reputation: 25518
I've just had the same problem and found this question when trying to find an answer.
What fixed this for me was disabling firebug lite in chrome. It was swallowing all console messages.
Upvotes: 48