On Friday, April 14, 2017 at 12:08:45 PM UTC+2, Naked Love wrote: > > Dear Sebastian, I appreciate that you are trying to respond to all the > queries and you are being politically correct but whatever it is, its not > firebug its dev tools or whatever, what matters is that it really sucks. > Firebug was the only reason I used to install Mozilla every time. It used > to make you more powerful while doing some development work. All the > firebug lovers will agree to that. >
It's great to hear that you love Firebug. So do I. And that's why I advocated for continuing Firebug as a separate extension in the discussions to integrate it into the Firefox DevTools and actually left the team when the decision was made <https://groups.google.com/d/msg/firebug-working-group/6PulwrKtmtE/QnxXJ6c4_AMJ> . Now I'm telling Firebug users to at least give the Firefox DevTools a try. While their UI is still not as good as Firebug's and I am also still missing several features, those tools are way better than their reputation and it's sad for me to see so many people move to Chrome just because Firebug doesn't work anymore. Every tool has it's advantages and disadvantages <http://stackoverflow.com/q/42504326/432681>, be it the Firefox DevTools, Firebug, the Chrome DevTools or any other browser developer tools. Please if possible put it back on. Whatever this new thing is, it just > sucks. I loved the old firebug it was a simple yet effective tool. > With the changes in Firefox regarding multiple processes <https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox> (aka e10s <https://wiki.mozilla.org/Electrolysis>) and Mozilla's decision to only support WebExtensions starting from Firefox 57 <https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/>, there is just no way that Firebug comes back. Background: E10s means separate processes for the browser UI and the website contents, i.e. better performance and stability for the browser, meaning when a page hangs, it doesn't freeze the Firefox UI anymore. Though it also means that extensions are required to use new message-based APIs to access the page's contents. Firebug's code accesses the page's contents directly in many different places, though, which would have required to rewrite the a huge amount of code. WebExtensions are an established way to write extensions that work cross-browser, i.e. this enables extension developers to write extensions that work in all browsers. While this is good for people that want to write new extensions, existing ones need to be adapted to the new APIs in order to continue to work. Also, WebExtensions have limited access to the browser internals, which makes them safer for users but at the same time doesn't provide the flexibility of existing extensions. Because Firebug is based on extension code (Add-on SDK), which will be deprecated once Firefox 57 is released, this would have meant to basically recreate it from skretch with less functionality. And the Firebug Working Group - mainly consisting of one full-time programmer and three volunteer contributors spending their free time working on it - simply didn't have the resources to do all that. Having said all that, you can disable multi-process Firefox <http://stackoverflow.com/a/40748127/432681> to get Firebug to work again temporarily until this feature can't be disabled anymore or Firefox 57 is released (depending on which one comes first). I've also outlined the alternatives you currently have regarding the Firefox DevTools <http://stackoverflow.com/a/41890636/432681>. Sebastian PS: Please refrain from hateful speech! Complaining about the DevTools doesn't bring back Firebug and the DevTools team doesn't follow this thread, anyway, so it's wasted time. On Thursday, February 9, 2017 at 12:03:36 AM UTC+5:30, Sebastian Zartner > wrote: >> >> There is no new Firebug, Firebug is discontinued. You got automatically >> switched to the Firefox DevTools (with a Firebug theme to make the >> transition a little easier). Please see the related Mozilla Hacks blog >> post >> <https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/> >> for more info and read the migration guide >> <https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug>. >> If you're missing something, please have a look whether it is already >> listed as blocker >> <https://bugzilla.mozilla.org/showdependencytree.cgi?id=991806&hide_resolved=1> >> >> of bug 991806 <https://bugzilla.mozilla.org/show_bug.cgi?id=991806>. If >> not, please file a new bug and mark it as blocker of that one. >> >> Sebastian >> >> On Wednesday, February 8, 2017 at 1:29:37 PM UTC+1, i...@pitertour.ru >> wrote: >>> >>> sad... >>> >> -- 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/c446f0a9-18f3-450f-9f61-140fd20bc5d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
