Comments on: MooBugger – the MooTools JavaScript Console

By: Aaron N.

Aaron N. — Wed, 11 Feb 2009 17:40:23 +0000

Not a bad idea. I’ll put it on my to-do list, but I’m not sure when I’ll get around to it… That list is getting long!

By: Guillermo Rauch

Guillermo Rauch — Wed, 11 Feb 2009 17:10:38 +0000

Aaron, I suggest you put up a demo page that disregards the presence of other loggers to inject MooBugger, for demonstration purposes.

By: ScottH

ScottH — Sat, 24 Jan 2009 02:49:20 +0000

Hi. Moobugger has no effect in Safari 2.0.4 (OS X 10.4.8). Nothing happens when I click the bookmark. I assume a console window is supposed to open?

I will try on another system (OS X 10.4.11 with Safari 3.2.1) later.

Thanks,

Scott

By: John Larson

John Larson — Fri, 23 Jan 2009 01:01:31 +0000

Sweet! Glad I could finally contribute something back. Totally grateful for your work here–between this and the mention of X-RAY, for example, it made my day of IE debugging slightly less painful!

By: Aaron N.

Aaron N. — Thu, 22 Jan 2009 19:29:12 +0000

Nice work! It's fixed. Thanks for figuring it out - I was just too busy this week to dig into it. I also added moobugger.zip to the directory.

By: John Larson

John Larson — Thu, 22 Jan 2009 19:07:35 +0000

Regarding the IE issue, I think one can pretty well fix the issue with one keystroke on line 162, add a “6″ to “Moo.Client.Engine.ie”:

if (Moo.Client.Engine.ie6) debug.iFrame.style.position = ‘absolute’;

Since IE7 supports fixed positioning (at least in strict mode) you’re all set without that special hack.

By the by, Aaron: regarding your earlier comment welcoming us to try debugging it ourselves, right on! I accepted the invite, but it did take a bit of hacking around to download the debugger.js as well as the supporting files (so as to install it elsewhere to play with a modified version). Do you have a zip of the whole package handy for us to play with/debug/build upon?

By: Aaron N.

Aaron N. — Tue, 20 Jan 2009 16:24:25 +0000

You should use my console wrapper: dbug.js – it’s designed to be left in your codebase and it can be enabled at will.

I’ll look into the IE issue.

By: samgoody

samgoody — Tue, 20 Jan 2009 09:49:22 +0000

Can confirm that it does not work properly on IE, moves up with the page. Though it did way back (I remember us laughing [via email] that this was happening on Maxthon).

Also, a warning should be made here, as well as on the Firebug site, that if you have all these console.log statements, and than you remove firebug lite/ Moobugger without removing the log statements, your site will break. As soon as it hits the first console.log the script will exit.

This should be obvious, but has bitten me at least once, so worthy of mention.

By: Ajaxian » MooTools Update: Milk, MooBugger, JavaScript techniques, and more

Ajaxian » MooTools Update: Milk, MooBugger, JavaScript techniques, and more — Fri, 16 Jan 2009 12:39:14 +0000

[...] MooBugger [...]

By: Aaron N.

Aaron N. — Thu, 15 Jan 2009 20:59:04 +0000

Hmm. It used to work, but it’s been a while since I actually used it in IE7. Perhaps I’ll spend a little time debugging it. You’re welcome to, as well, of course.