> It seems that certain types of error messages cause a problem with
> Firebug's console display.

> Please see attached screenshot.

> I'm using Firefox 13.0 with and Firebug 1.9.2.

> Sorry for the confusion regarding the highlighting, folks; I thought it
> would make the issue easier to see.

> I upgraded to Firebug 1.10.0a11, but the issue persists.

> The issue seems to be related to or caused by a particular JavaScript file
> ( https://gist.github.com/1045906 ), which seems to be included in many
> different "boilerplate" packages.

> The version I was using is probably over a year old; when I upgraded to
> the current version (at the above-cited URL), the issue disappeared.

> For academic/debugging purposes, here is the older version of the script
> that was causing the problem:

> ----------
> // usage: log('inside coolFunc', this, arguments);
> // paulirish.com/2009/log-a-lightweight-wrapper-for-consolelog/
> window.log = function(){
>   log.history = log.history || [];   // store logs to an array for
> reference
>   log.history.push(arguments);
>   if(this.console) {
>     arguments.callee = arguments.callee.caller;
>     var newarr = [].slice.call(arguments);
>     (typeof console.log === 'object' ? log.apply.call(console.log,
> console, newarr) : console.log.apply(console, newarr));
>   }
> };

> // make it safe to use console.log always
> (function(b){function c(){}for(var
> d="assert,count,debug,dir,dirxml,error,exception,group,groupCollapsed,group End,info,log,timeStamp,profile,profileEnd,time,timeEnd,trace,warn".split(", "),a;a=d.pop();){b[a]=b[a]||c}})((function(){try
> {console.log();return window.console;}catch(err){return
> window.console={};}})());
> ----------

> The last line is the line that is referenced in the Firebug console error
> output.

> I'm not sure what, exactly, was triggering that function in the first
> place, but it seems to be some kind of conflict between FancyBox 2.5 and
> jQuery.

> If I can be of further assistance, please do let me know.

> Thanks for the help!

> console.log();
> console.log();
> console.log();

> On Jun 24, 11:23 pm, alfonsoml <aml...@gmail.com> wrote:
> > Reproducing this bug is easy, just call log without arguments:

> > console.log();
> > console.log();
> > console.log();

> Ah, I see.

> In such case, we could perhaps display a message (i gray color)
> saying something like: "no message provided".

> What do you think?

> Could you please create an issue report for this?
> http://code.google.com/p/fbug/issues/list

> Thanks for the test case!
> Honza

> console.log();
> console.log();
> console.log();