Why does IE implement console.log() differently from Safari, Chrome, and Firefox
If you use console.log() with out checking for its existence it breaks the code in IE.  Once you go into debug it using the debugger....it begins to work masking the actual issue.

Because of this Catch-22 you never get to see the actual fail.

This is not a problem in Safari, Chrome, and Firefox.

Where can I file this as a bug ( a very ambiguous one ) and why does IE do this?
Why does IE implement console.log() differently from Safari, Chrome, and Firefox
===

If you use console.log() with out checking for its existence it breaks the code in IE.  Once you go into debug it using the debugger....it begins to work masking the actual issue.

Because of this Catch-22 you never get to see the actual fail.

This is not a problem in Safari, Chrome, and Firefox.

Where can I file this as a bug ( a very ambiguous one ) and why does IE do this?