script none

[Alexandr Ivanov]

Mozilla version 50. No view script page.

[Дмитрий Федоров]

+
Script tab doesn't work in FF v.50

[Sebastian Zartner]

Firebug is now merged into the Firefox DevTools and the development of Firebug as extension is discontinued, therefore it is likely that parts start to break with newer versions of Firefox.
You should try out the Firefox DevTools instead.

Sebastian

[David Gomez]

>Firebug is now merged into the Firefox DevTools

This has to be a joke.

Multiline Console, firequery, events panel, console.group,...............

"Firefox DevTools" is not a substitute, that's just something they have imposed on us

[Sebastian Zartner]

On Thursday, November 17, 2016 at 1:15:53 PM UTC+1, David Gomez wrote:

>Firebug is now merged into the Firefox DevTools

This has to be a joke.

Multiline Console

Is available as "Scratchpad". Also, you can write multi-line scripts directly into the command line by pressing Shift+Enter.
 

firequery

Got ported to the DevTools.
 

events panel

Events can be displayed by clicking the 'ev' icon next to an element. Besides that there is also a request to add an Events panel like in Firebug.
 

console.group

Works the same as in Firebug, as well as all the other functions of the console API. Only the output doesn't look the same in all cases, for which I've filed a bug.
 

"Firefox DevTools" is not a substitute, that's just something they have imposed on us

The switch to multiple processes in Firefox would have required huge changes to the Firebug codebase and the Firebug Working Group didn't have the resources to compete with the DevTools, so the decision was made to merge it. I was not happy with that decision, so I left the team.

Having said that, the Firefox DevTools got quite powerful over the years. In my opinion, their UX is still not as good as Firebug's, but therefore they have a lot of features Firebug (and also the Chrome Devtools) is missing. So it's definitely worth trying them out.
The Firefox DevTools team is also trying to close the gaps between their tools and Firebug (see bug 991806). So, if you're missing something Firebug had, you should file it as a blocker of that bug.

Sebastian

[David Gomez]

> Is available as "Scratchpad".

The firebug console is much more comfortable, I do not think it's a replacement

> firequery

It does not work and nobody is interested in fixing it: https://github.com/firebug/firequery/issues/39

>Events can be displayed...

 Firebug is more comfortable

>console.group. Works the same as in Firebug

No, they do not work the same. Groups are not collapsible. The console has become unusable

There are many, many more differences...

>Firebug Working Group didn't have the resources...

Yes I know. But the solution I think is to make the team bigger, but it was decided to start a new project, and that's the problem. There are a lot of people now trying to make Firebug work because the DevTools are not a valid replacement

[Sebastian Zartner]

On Thursday, November 17, 2016 at 2:04:08 PM UTC+1, David Gomez wrote:

> Is available as "Scratchpad".

The firebug console is much more comfortable, I do not think it's a replacement

I agree that Firebug's Command Editor UI is better in several ways, though Scratchpad is usable. I think there was some request for a "multi-line command line" like in Firebug, though I can't find it right now.
 

> firequery

It does not work and nobody is interested in fixing it: https://github.com/firebug/firequery/issues/39

I didn't try it myself lately, though one of the bugs linked in the issue is already fixed and the other one is assigned. So it will hopefully be fixed soon.
 

>Events can be displayed...

 Firebug is more comfortable

Yes it is, that's why an Events side panel was requested. Non-the-less, the tooltip, which opens when you click the icon shows the related events (even jQuery events like in Firebug).

>console.group. Works the same as in Firebug

No, they do not work the same. Groups are not collapsible.

Groups are not collapsible in the stable release (Firefox 50.0), though in Nightly (Firefox 53.0a1) they are. But, of course, it's somewhat poor that they were initially implemented without being collapsible.
 

The console has become unusable

General complaints like this one don't help anybody. You should tell the DevTools people what needs to be improved to make it usable for you.
 

There are many, many more differences...

Sure, and I and others already filed a lot of those against bug 991806.
 

>Firebug Working Group didn't have the resources...

Yes I know. But the solution I think is to make the team bigger, but it was decided to start a new project, and that's the problem.

I'm not happy about Mozilla's decision to create a separate set of tools instead of putting more resources into the Firebug project. That decision had advantages and disadvantages. Anyway, it can't be changed now.

There are a lot of people now trying to make Firebug work because the DevTools are not a valid replacement

And I am trying to help people to do so. Though again, this won't work forever, because Firebug doesn't work anymore once multi-process Firefox is enabled.

Firebug is an open source project and lived from contributions by volunteers. Unfortunately, while Firebug had and still has a huge community of users, there was only a handful of people contributing to the project.

Anyway, as it stands now, the Firebug as extension is discontinued. So, either users start switching over to the Firefox DevTools or to the Chrome DevTools.
Of course, Firebug is still open source, so if someone wanted to revive it, nobody would stop them to do so. Though I believe at this point it makes more sense to put the efforts into the DevTools and try to make their usability as good as Firebug's.

Sebastian

[David Gomez]

> So it will hopefully be fixed soon.

What's is soon? 6 weeks, 12, 18, ...? I thinks that it's no sense

> From https://groups.google.com/d/msg/firebug/NujWavcUpwk/7u8U9c-0AAAJ

> From my experience they mostly listen to their users.

Wow! Whats about Unsigned Add-ons? Whats about Australis? 

Whats about "remove version information in the Firefox add-on manager" https://bugzilla.mozilla.org/show_bug.cgi?id=1175324

IMO they don't listen to their users.

> Groups are not collapsible...Firefox 53.0a1

Another one. Release date from  Firefox 53 is 2017-04-18 (https://wiki.mozilla.org/RapidRelease/Calendar). Several years later

> General complaints like this one don't help anybody. 

You are right, but Mozilla does not want my help

>either users start switching over to the Firefox DevTools or to the Chrome DevTools.

That's the point. Chrome DevTools is better than Firefox DevTools. 

More things: Mozilla will remove XUL and XPCOM support . https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/

and Mozilla will look more and more like Chrome, ... Mozilla  has lost their mind.

Sorry for this complaint, you aren't responsible of this crazy decisions

[Sebastian Zartner]

On Friday, November 18, 2016 at 9:13:46 AM UTC+1, David Gomez wrote:

> From https://groups.google.com/d/msg/firebug/NujWavcUpwk/7u8U9c-0AAAJ

> From my experience they mostly listen to their users.

Wow! Whats about Unsigned Add-ons? Whats about Australis? 

Whats about "remove version information in the Firefox add-on manager" https://bugzilla.mozilla.org/show_bug.cgi?id=1175324

I was talking about the DevTools team, not Mozilla in general.
 

IMO they don't listen to their users.

Of course there are always things to complain about. I also have several issues I believe Mozilla made wrong decisions about or set the priorities wrong.
Though making decisions is hard and you can't make everyone happy.
 

> General complaints like this one don't help anybody. 

You are right, but Mozilla does not want my help

From my own experience contributions are very welcome, especially patches.
 

Sorry for this complaint, you aren't responsible of this crazy decisions

I can understand you, though I'm not a Mozilla representative nor can I address your complaints. And this discussion already went far beyond the scope of Firebug.

So, let's stop this discussion here.

Sebastian