trace broken in Firefox

[fholzer]

Tested with Firefox 41.0.1, loglevel 1.4.0.
To reproduce, go to https://jsfiddle.net/zLsjmg2d/2/ in Firefox and open console.
Expected result: console should show trace log messages.
Actual result: console shows "console.trace():"

[pimterry]

Ah, interesting, yes. That's poor behaviour on Firefox's part; they're not following the (admittedly draft) spec, which says it should behave as console.log, but with a stack trace too.

Here instead it just prints a stack trace, but ignores any provided messages. I'm not really sure about what to do with that. There is a bug filed in Firefox for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1172314

The easiest option is to declare Firefox badly behaved, and ignore it until it gets fixed. I expect that's not too helpful for you though. I would be happy to add a workaround to also console.log() the message, if you can find some way to detect this situation? I'm not sure of any easy ways to do that though, and I don't want to start duplicating the messages in every other situation (which seems like the only other option). Any suggestions?

[xDaizu]

Just hit my head several times against the keyboard because of this issue (I thought I was using it wrong) before I thought of checking this "issues" section.

My suggestion is beating Firefox people up with a stick. Also HUGE bold informative disclaimer on the documentation section of this project.

[pimterry]

Returning to this a few years later: I've noticed that Firefox actually fixed this a year ago, in version 64: https://bugzilla.mozilla.org/show_bug.cgi?id=1172314.

I've now updated the docs to reference that. Since this doesn't apply to recent Firefox releases, old Firefox usage is rare, and this isn't a showstopping bug, I'm going to close this issue now. Thanks everybody!