On Wednesday, March 29, 2017 at 6:14:19 PM UTC+2, San wrote: > > On Wed, Mar 29, 2017 at 6:56 AM, M Gol <mikg...@gmail.com <javascript:>> > wrote: > >> ... i don't get it, up until a few days ago firebug was awesome, now >> automatically it's crap because it's discontinued? Can I still use the old >> (good) one, even though it's discontinued, if i promise to not call >> support? I never have in the last x years i've been using it, but this new >> one is worse than chrome's dev tools :s sorry >> >> > Nobody here is saying that Firebug is "crap"... just that it doesn't work > anymore with the newer versions of Firefox. >
Just to clarify this again. There is no "new Firebug". What you are seeing are the Firefox DevTools using a Firebug theme <https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/>. Anything that you had in Firebug and you're now missing in the DevTools and that is not yet filed <https://bugzilla.mozilla.org/showdependencytree.cgi?id=991806&hide_resolved=1>, should be suggested in the related thread <https://groups.google.com/d/topic/firebug/Q6eyvGt6hyI/discussion>. Also I'm not aware that there was ever a way to "call support" -- what > support? This is just a user forum, by the way, not an official Mozilla > forum. > It is the official Firebug forum, though, where Firebug users were meant to get help. But it's correct that this is not a Mozilla forum. The only way to get Firebug to work again is to roll back Firefox to an > earlier version and stay there (don't update FF anymore). > There are actually more alternatives to the Firefox DevTools <http://stackoverflow.com/a/41890636/432681>. If you want to get back Firebug (temporarily, until multi-process Firefox becomes mandatory), I've described how you can do this on Stack Overflow <http://stackoverflow.com/a/40748127/432681>. > Which I'm probably going to do anyway within the next few months... > because the people who control FF are going to kill off far more than > Firebug. They're planning to kill almost the entire FF extensions > architecture (XUL). That will break my entire development environment, > which relies on numerous extensions plus custom scripts I wrote to tie them > together. Mozilla is planning to replace the current extensions environment > with Chrome's inferior system. > >From my point of view, this means that Firefox is going to commit suicide > later this year. > To give some background, Mozilla plans that Firefox 57 (shipping in November 2017) will only support WebExtensions <https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/> and drop support for legacy extensions, which means that most current Firefox extensions won't work anymore at that point. Firefox will provide advanced APIs (actually does already) over the ones of Chrome (and other browsers), though extensions will still need to be ported to the new architecture in order to continue work. 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/a11df793-5226-4f77-9bf6-345eb225d413%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
