Re: [firebug] Re: Firebug 2.0.19

[Sebastian Zartner]

See my answer on Stack Overflow

.

Sebastian

On 29 March 2017 at 02:16, M Gol  wrote:

> Is there any way to go back to the old firebug?
>
> On Wednesday, March 1, 2017 at 11:23:45 PM UTC+11, Jan Honza Odvarko wrote:
>>
>> Firebug 2.0.19 released (maintenance release)
>> https://blog.getfirebug.com/2017/03/01/firebug-2-0-19/
>>
>> Honza
>>
>>
>> --
> 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/ea319eb7-e116-419a-bc18-40b7bdfdca06%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAERejNZ8dffqYCS%3D2KZWEQ4MymmZfO4jwKjs9M063JH-0oMbWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0.19

[Sebastian Zartner]

On Thursday, March 16, 2017 at 3:27:38 PM UTC+1, Ole Laursen wrote:
>
> Hi!
>
> I just discovered today that my Firebug console is broken.
>

I've posted a related answer on Stack Overflow 
.
 

> 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?
>

I've added a comment to bug 1337701 
, which seems to be 
very similar.

(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.)
>

Yeah, the Firefox DevTools work quite well already, they mostly just need 
some UX fine-tuning.

On Thursday, March 16, 2017 at 3:27:38 PM UTC+1, M Gol wrote:
>
> 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.
>

Firebug 2.0.19 only changed an unrelated part, so I assume you have 
multi-process Firefox enabled and by that already got automatically 
switched to the Firefox DevTools. See 
https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/ for 
more info.
Having said that, the CSS does get updated in real time when you edit it 
within the *Rules* side panel. It doesn't get updated automatically, 
though, when you edit the style attribute within the HTML structure. That's 
covered in bug 815464 .

Sebastian

-- 
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/3477f7b7-e0d2-460a-ba04-b5b364c51f65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0.19

[Ole Laursen]

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.)


Ole

-- 
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/177ca5d1-69c4-46ae-8b76-ed82da688642%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0.19

[Sebastian Zartner]

On Thursday, March 9, 2017 at 8:12:41 AM UTC+1, San wrote:
>
> 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
>

Pressing F12 while Firebug was open minimized it (letting Firebug run in 
the background) just like the minimize button did.
 

> 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.
>

That badge was shown whenever Firebug was activated, independently of 
whether it was minimized. The DevTools have this feature in their Developer 
Toolbar 

.
 

> (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.
>

I've mentioned that in the bug 
.
 

> OTOH, the Firefox DevTools seem to be completely turned off if they aren't 
> displaying any windows.
>

Correct.
 

> 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.
>

I don't use MacOS, but minimizing means to keep them on in the background.

But please let's rather discuss such things in the related bug report(s).

Sebastian

-- 
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/f79dd1b9-e1e0-417a-a194-a23bbdf703f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [firebug] Re: Firebug 2.0.19

[Lawrence San]

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.

-- 
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/CAMoMLKguFAbr2AVYkT%2BC29Zp%3DuWSv%2BmaEiozJnJ36YP3X%3DP2gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.