Illegible ("squished") JavaScript errors in Firebug console

[Ben]

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.

[Sebastian Zartner]

I believe this error is not caused by Firebug. The Firebug Console doesn't have messages with yellow background by default.
To check this you may disable all the other extensions and try it again.

Sebastian

[Jan Honza Odvarko]

On Jun 21, 11:11 pm, Sebastian Zartner

<sebastianzart...@googlemail.com> wrote:
> I believe this error is not caused by Firebug. The Firebug Console doesn't
> have messages with yellow background by default.
> To check this you may disable all the other extensions and try it again.

The yellow background is added, I guess (to highlight the text).

Ben, two questions:
1) can you provide a test case so, we can reproduce on our machines
and fix?
2) can you test with Firebug 1.10a11?

http://getfirebug.com/releases/firebug/1.10/firebug-1.10.0a11.xpi

Honza

[Sebastian Zartner]

The yellow background is added, I guess (to highlight the text).

My fault. I didn't have a careful look before to see that the background is not strait but a marking.

Sebastian

[Ben]

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,groupEnd,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!

[alfonsoml]

Reproducing this bug is easy, just call log without arguments:

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

[Jan Honza Odvarko]

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

[alfonsoml]

Ok, I've created http://code.google.com/p/fbug/issues/detail?id=5615
Whatever solution you decide is right for me :-)

Thank you.

[Jan Honza Odvarko]

On Jun 25, 8:45 am, alfonsoml <aml...@gmail.com> wrote:
> Ok, I've createdhttp://code.google.com/p/fbug/issues/detail?id=5615

> Whatever solution you decide is right for me :-)

Alright, thanks for the report!
Honza

[Jan Honza Odvarko]

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();

Patch committed, should be fixed in Firebug 1.10 beta 2

Honza