On Thursday, March 2, 2017 at 3:18:07 PM UTC+1, Segei wrote: > > Want to absolutely second the console.log sentiment! Can't wrap my head > around how this absolutely indispensable feature not working has not > resonated at all (googling it brings up nothing). That and the fact that > the Script tab is dead seem like the two most important things making FB > practically unusable. > I guess the silence is a sad reminder of how few devs still use Firebug. >
Searching for "firebug console not working" gives a lot of current results. And there are several related questions on Stack Overflow, I've posted answers <http://stackoverflow.com/a/42515910/432681> to two of them <http://stackoverflow.com/a/41934776/432681>. > I realize that it's been discontinued, but restoring the console.log is > probably simple and will make a lot of (well, maybe just some) folks very > happy! > It looks like a Firefox internal API has changed. I didn't have a deeper look, but if it's a completely new API, this might require bigger changes. Anyway, Firebug is still open source <https://github.com/firebug/firebug> and I guess if someone provides a patch for this, there could be another release. > I guess I could even do without, if the native FF devTools with its new FB > design finally had a multi-line side pane in the console. > There's currently no multi-line command editor like in Firebug unfortunately (requested in bug 1133849 <https://bugzilla.mozilla.org/show_bug.cgi?id=1133849>), but the command line in the DevTools allows to enter multi-line commands and they also provide a JavaScript editor called Scratchpad <https://developer.mozilla.org/en-US/docs/Tools/Scratchpad> (has a somewhat poor UX for the output at the moment, though). > That, coupled with the much friendlier elements view, are probably the two > most important things where FB is shines compared to Chrome's devTools, and > yet no clue when this will be added (if at all). > If you have anything Firebug did better than the Firefox DevTools that's not already filed <https://bugzilla.mozilla.org/showdependencytree.cgi?id=991806&hide_resolved=1>, please create a new bug report and mark it as blocking bug 991806 <https://bugzilla.mozilla.org/show_bug.cgi?id=991806>. Sebastian > On Wednesday, March 1, 2017 at 8:35:40 PM UTC+2, San wrote: >> >> It's nice that you fixed this for those of us with e10s disabled... but I >> don't understand why you bothered to fix this but not something else >> equally important (more important to me) -- I mean that the Firebug Console >> no longer displays anything at all. Without the Console, Firebug is >> useless, so why bother fixing anything else? >> >> [ edit: I said "Firefox" when I meant "Firebug". Sorry.] >> > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/0a68c020-e1a0-49c9-97ac-d9958e987064%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
