News for hackers. Stuff that matters.
Re:Firefox 31 for developers by bellerocky on Wednesday July 23, 2014 @11:40AM (#8074945)
Something I don't get about the Firefox developer tools is why they make the console logging unavailable if I've defined console as a window level variable, overwritten for the purposes of extending its behavior.

This only happens for the Firefox tools. Firebug, Safari and Chrome web inspector don't care. We do this so we can enable and disable console statements for debugging purposes. We monkey patched console, and because of that I can't use Firefox developer tools at all. It's a shame.

Re:Firefox 31 for developers by mnemonik on Wednesday July 23, 2014 @12:01PM (#8075053)
Works for me:

    > c = console
    Console {  }
    > window.console = {}
    Object {  }
    > c.log("hello")
    undefined
    "hello"
If you could provide specific steps-to-reproduce and/or a test case, then dropping those in a bug is the best way to get the behavior fixed: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...
Re:Firefox 31 for developers by McGlockenshire on Wednesday July 23, 2014 @12:02PM (#8075058)
Have you created a minimal test case and filed a bug?