39

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.

James McMahon
  • 48,506
  • 64
  • 207
  • 283

9 Answers9

48

Make sure you have the console showing and that it is showing "All".

The cursor is on the button to hide/show the console.

alt text


Update: In newer versions of Chrome, you need to click the filter icon, then make sure "All" is selected.

console filter

Glorfindel
  • 21,988
  • 13
  • 81
  • 109
Mottie
  • 84,355
  • 30
  • 126
  • 241
48

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.

sf.
  • 24,512
  • 13
  • 53
  • 58
20

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.

brent5000
  • 973
  • 2
  • 8
  • 11
  • 1
    The only thing I see under “Extensions” is “Tweetdeck,” there is nothing about inspecting active views. – Brandon Rhodes May 25 '11 at 14:53
  • 2
    Now it's right-click on the pop-up and click 'inspect popup'. See: http://code.google.com/chrome/extensions/tut_debugging.html – Thariq Shihipar Nov 09 '11 at 04:00
  • 1
    and the log from content_script can be seen directly in the page's console cause content_script is embedded in the page's content – DiveInto Feb 19 '12 at 05:11
  • It's changed again - you now go to the list of Extensions, find the one you want console messages for, and look for "Inspect views" with some giant links next to little text. The background page(s) for the extension will be linked there, and clicking them brings you not to a page but rather opens the Developer Tools window for that page, and there you'll see the console messages. Confusing for sure. – Chris Moschini May 24 '13 at 00:47
5

On my computer I had accidently clicked the Debug filter. This made my log messages hidden. Here's how it was before (hidden messages): Chrome log not showing messages

Here's how it was after the change (working messages): enter image description here

3

I just found out logging was disabled from my filters.

filters with logging

fer
  • 1,016
  • 1
  • 10
  • 20
3

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.

Ajai Singh
  • 57
  • 2
  • 1
    In my case, I forgot I had Firebug Lite installed on the page but hidden... it was intercepting all the logging despite having the setting overrideConsole set to false... – andrhamm Sep 02 '11 at 13:59
0

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.

payne
  • 4,691
  • 8
  • 37
  • 85
0

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.

tutug
  • 421
  • 4
  • 5
0

I have this error by have obfuscated javascript code, deobfuscate and console.log work again)