Firebug 2.0.13

[Jan Honza Odvarko]

https://blog.getfirebug.com/2015/10/26/firebug-2-0-13/

Honza

[pd]

Thanks to everyone for their work in continuing to keep Firebug going. I personally see Firebug as still very superior to the native DevTools (or whatever they're called) in many ways for my usage at least and would be hugely hampered by it's demise.

So thanks again everyone! I wish I had the time/energy to contribute to Firebug's development.

On Tuesday, October 27, 2015 at 12:27:36 AM UTC+11, Jan Honza Odvarko wrote:

https://blog.getfirebug.com/2015/10/26/firebug-2-0-13/

Honza

[Mike Velasco]

Hi,

I work at a company that requires a review of the source code before usage of each version of Firebug.  In the past we have pulled source code from GitHub.  However 2.0.13 does not appear as a tagged release on the list linked below.  Can someone add the tag for this release in GitHub?  Thank you in advance!

https://github.com/firebug/firebug/releases

-Mike

[Sebastian Zartner]

Hi Mike,

I've created them.

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+u...@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/5b4494a7-e9d5-4ebd-8eea-307cc9c448e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Invixious Nefarious]

I did not notice that 2.0.13 does not work with FireFox 43.0.4 until it was too late.  My dev system is isolated from the internet, and FireBug will remain disabled unless/until I can get it verified.

a) Do you know if/when 2.0.13 will become compatible with FF 43.0.4?

b) Are you aware of any workarounds?  I really love FireBug, and have gotten to the point where I cannot troubleshoot many issues without FireBug.

V/r,

IN

[Mike Velasco]

Thank you Sebastian!

-Mike

[Erik Krause]

Am 22.01.2016 um 19:05 schrieb Invixious Nefarious:

> a) Do you know if/when 2.0.13 will become compatible with FF 43.0.4?

This combination works perfectly here on Win 7 64

Specify "does not work"...

--
Erik Krause
http://www.erik-krause.de

[Sebastian Zartner]

You need to go to about:config and set the preference xpinstall.signatures.required to false.

Though note that this preference will be removed in Firefox 44, which will be released tomorrow. Starting from that version, you are forced to install the DevEdition, Nightly or an unbranded version of Firefox.

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+u...@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/56A66C4E.3000202%40gmx.de.

[Lawrence San]

On both Mac and Win7, Firebug 2.0.13 + Firefox 43.0.4 seem to be working mostly okay for me.

I just checked about:config for the signatures flag that Sebastian referred to, which I don't remember changing. The xpinstall.signatures.required has _not_ been user-altered: it's still set to true. However, there are some bolded (user-altered) items referring to xpinstall.whitelist.etc.... which I don't remember adding or changing. Is it possible that I whitelisted Firebug as specifically exempt from the signatures requirement, and just don't remember? How can I see what was already whitelisted? (Double-clicking those items just brings up a dialog asking me to enter a string value; I'd like to see the current whitelist.)

[Sebastian Zartner]

According to some very old release notes the xpinstall.whitelist.required and xpinstall.whitelist.add preferences are only for whitelisting websites for add-on download. Though, I think those preferences are not used anymore, because they don't change when I allow the installation of an add-on from a website and the next time I want to install an extension from that website I'm asked again if I want to allow that.

Also, I just read a blog post on the Mozilla website stating that the removal of the xpinstall.signatures.required preference was deferred to Firefox 46. There is also a timeline with some more information about extension signing.

Sebastian

[Erik Krause]

Am 26.01.2016 um 07:15 schrieb Sebastian Zartner:
> Also, I just read a blog post on the Mozilla website

> <https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/> stating

> that the removal of the xpinstall.signatures.required preference was
> deferred to Firefox 46.

Does this mean FB 2 will stop working in FF 46? With no adequate
replacement? Or is there any hope FB 3 will have all the current
functionality (including the plugins) until then?

[Jan Honza Odvarko]

Firebug 2 will stop working when you start using it with multi-proccess browser (code name: e10s activated). The current plan (it's still changing) is to enable e10s for Firefox 47.

When that happens you have the following choices:
1) Open built-in Firefox devtools (Tools -> WebDeveloper -> Toggle Tools)
2) Try Firebug.next https://github.com/firebug/firebug.next/releases
But the XPI isn't signed, so you need to flip the pref: xpinstall.signatures.required
3) Switch of the e10s (not recommended)

In the meanwhile we are working hard to have all Firebug features part of built-in Firefox DevTools so, Firebug users can easily switch and feel at home.

Honza

[Erik Krause]

Am 26.01.2016 um 17:16 schrieb Jan Honza Odvarko:
> In the meanwhile we are working hard to have all Firebug features part of
> built-in Firefox DevTools so, Firebug users can easily switch and feel at
> home.

That'll be a long way to go. If all changes go with the speed of f.e.
bug https://bugzilla.mozilla.org/show_bug.cgi?id=1031192 I'm pessimistic...

[Jan Honza Odvarko]

On Tuesday, January 26, 2016 at 5:30:51 PM UTC+1, Erik Krause wrote:

Am 26.01.2016 um 17:16 schrieb Jan Honza Odvarko:
> In the meanwhile we are working hard to have all Firebug features part of
> built-in Firefox DevTools so, Firebug users can easily switch and feel at
> home.

That'll be a long way to go. If all changes go with the speed of f.e.
bug https://bugzilla.mozilla.org/show_bug.cgi?id=1031192 I'm pessimistic...

I know, sometimes it takes time, but we are doing what we can.

Honza

[Erik Krause]

Am 26.01.2016 um 17:35 schrieb Jan Honza Odvarko:
> I know, sometimes it takes time, but we are doing what we can.

Do you also work on the front end? Storage inspector still looks awful,
lines jump arbitrarily to the end if clicked, details view overlaps and
can't be switched off...

[Jan Honza Odvarko]

On Tuesday, January 26, 2016 at 6:12:19 PM UTC+1, Erik Krause wrote:

Am 26.01.2016 um 17:35 schrieb Jan Honza Odvarko:
> I know, sometimes it takes time, but we are doing what we can.

Do you also work on the front end?

Yes, and btw. one part of the plan is to use ReactJS to build the UI.
This should allow us to build (and also maintain) better even more complex UI.
I truly believe that this will also lead towards better user experience.
 

Storage inspector still looks awful,
lines jump arbitrarily to the end if clicked, details view overlaps and
can't be switched off...

It needs more love yes. I don't know about priority in this particular case, but the bug you brought up
is the best place where to provide feedback and ask ...

Honza