Comments on: Logging Information to the Firebug JavaScript Console

By: Slavka

Slavka — Sun, 23 Jan 2011 21:10:55 +0000

There are problems with console logging in different browsers.
Firefox has graete firebug.
http://getfirebug.com/wiki/index.php/Console_API
But firebug has a lot of functions towork withs CSS. Unuse in Js debagging.
More than oher browsers support firebug.js in different ways.

I wrote short script for basic console.API. It redefine most of console.xxx methods to put logs(warnings,timers,info, group) to
This console work on IE6+, FF, Chrome, Safari, Opera.
Press ‘~’ to show/hide them
http://dez.in.ua/console/light.html
http://dez.in.ua/console/

Console supply
• console.log(message);
• console.info(message);
• console.warn(message);
• console.debug(message);
• console.error(message);
• console.group(marker);
• console.group();
• console.groupCollapsed();
• console.groupCollapsed(marker);
• console.groupEnd(marker);
• console.groupEnd();
• console.time(marker);
• console.timeEnd(marker);
• console.clear();
in all – IE6+, Chrome, Safari, Opera, FF( still work with FireBug, but done all console. requests).

By: doz

doz — Tue, 09 Nov 2010 12:57:39 +0000

Hi,

If you had a flattr button i flattred you !

Thanks

By: David

David — Mon, 15 Feb 2010 04:06:17 +0000

David, just like the david before me (wow, this is getting confusing), your blog is awesome! It has taught me alot about mootools and javascript in general. Anyways, i decided to stop being a nub and use firefox’s console to log things and i came across your blog. I liked it so much I wrote an entry combining a couple of your entries onto my blog. Keep up the good work!

By: David

David — Fri, 05 Jun 2009 15:06:15 +0000

Ensuring that your console.xxx() calls don’t throw errors when the code runs outside of a Firebug environment was always a concern of mine. The four options for handling it that I have seen are:

Remove the comnsole.xxx() calls before publishing, as noted by the first two commenters above.
if (!window.console){ window.console.log = function {}; }
if (!window.console){ window.console.log = function { // real implementation here }; }
window.console && console.log(‘My message to the console.’);

Lately, I confess I’ve been doing a combination of (1) and (4). (1) keeps the code as lean as possible, but (4) allows me to miss a few without risking an error.

[ BTW: Dave, I'm new to your blog, but just can't say enough positive about it. The content, the look, the style. Just right freaking on. You might even have me sold on MooTools, as well. My investment in jQuery on a few projects is probably just at the level where I could conceivably back out and go with MooTools. But that's a whole different discussion for another time. Anyway, thanks and kudos on the site. ]

By: david

david — Mon, 11 Aug 2008 17:18:29 +0000

@anurag: Good question — I couldn’t find anything.

By: anurag phadke

anurag phadke — Mon, 11 Aug 2008 16:24:36 +0000

Is there a way to output the “Net” log to a file on my local machine? i.e. I want to output to a file all the URLs of images/swfs/text etc. that get loaded when a page is requested by the user.

By: pfwd

pfwd — Sat, 26 Jul 2008 09:01:13 +0000

Thanks for posting. I only knew of console.log untill now.

By: david

david — Fri, 25 Jul 2008 18:37:21 +0000

Thanks for the tips! I know that you can mess with Firebug a little with this:

http://davidwalsh.name/how-to-sniff-firebug-disable

By: Braxo

Braxo — Fri, 25 Jul 2008 16:33:42 +0000

When removing the console calls I do a simple find and replace of ‘console.’ with ‘//console.’

Plus, I know console.log can be used the same way in Safari’s developer window.

By: Sean O

Sean O — Fri, 25 Jul 2008 13:26:37 +0000

Using Firebug’s console() can be quite helpful. Just remember to remove calls to it before going to production as, surprisingly, IE will kick out JS errors aplenty. Or remember to use firebugx.js.