--
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+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@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/059e81ea-cafd-458b-99fe-eb3613ba8fba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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.
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!
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.
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).
AFAIK, Firebug's minimize button was more than simply an alternative to f12. Firebug was capable of running in the background even when it had no windows showing
and I seem to vaguely remember it could even show a "badge" on the icon (button) with a numeral warning of errors in the current web page.
(Or am I confusing it with some other tool I used?) Also the icon would turn gray if all the panels were disabled, or orange if at least one panel was enabled (in the background) and keeping track of something.
OTOH, the Firefox DevTools seem to be completely turned off if they aren't displaying any windows.
If that's correct, would adding a Dock button ("Dock" is MacOS toolbar) mean that the DevTools were always on in the background -- for example to keep track of errors, network activity, reflows, etc. -- for example, writing to the Console even though no panel was showing -- or would it simply be a static button to turn the DevTools "On" + open a window? That seems like two very different things.
Hi!
I just discovered today that my Firebug console is broken.
I tried the built-in one from a latest nightly build, but the output seems to be slightly inferior for common stuff, like printing an array with PODs. For instance, console.log([{ a: 1 }]) yields an entirely unhelpful Array [ Object ] instead of [{ a: 1 }]. By unhelpful, I mean, if I log three arrays to compare them, with Firebug I could immediately see any differences.
This seems to be a gap - do you know if there's a bug open on it? Or is the gap thing over now that Firebug is dead?
(BTW, it's annoying with a regression like this, but overall I'm happy to see better debugging included in Firefox, Firebug has had its share of bugs over the years from underlying changes in Firefox.)
Hello there, I'm a big fan of firebug and have been using it for years as a software developer.
I like the new update and it has lots of good ideas, but one thing that I see is missing in the latest version is having css (class and style) changes happen in real time, as I edit them in firebug.
--
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+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@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/ea319eb7-e116-419a-bc18-40b7bdfdca06%40googlegroups.com.