I can also just speak for myself, though as Lawrance already stated, Firebug will continue to exist and it will be integrated into the Firefox built-in devtools. The goal is to adjust their UI to look and work like Firebug. Furthermore Firebug 3 uses the Add-on SDK and is already prepared for the multi-process Firefox (Electrolysis). And to correct William's statement: The blog post says Add-on SDK based extensions will continue to work as long as they don't access the content process directly, i.e. if they are multi-process compatible.
If you are uncertain how Firebug.next works, you can try out a Firebug 3 alpha: https://getfirebug.com/releases/firebug/3.0/ (If you are using Firefox Beta, Dev Edition or Nightly, ensure you set xpinstall.signatures.required to false to be able to install it.) Sebastian On Monday, August 24, 2015 at 6:57:37 AM UTC+2, William Nerini wrote: > > These are also the concerns I have. Even with the DeveloperToolbar on > Chrome I find its developer tools to be a joke. Same for Firefox's built-in > tools. I'm already getting those warnings, as well, for several of the > extensions I run, most importantly, PrivacyBadger. > > I've seen the "Firebug.next" comments, but they're obscure, to be kind, > and I really need to understand whether I'm going to have to stand still, > for a bit, on my browser/tools for development. > > I suppose PaleMoon will be my only alternative, as a regular browser user, > looking for a flexible, configurable browser, but that doesn't necessarily > solve my problems as a developer: I do extensive client-side app > development in JavaScript (I'm writing a Virtual Tabletop for Pen and Paper > RPGs at the moment, at the moment) and would be dead in the water, using > FF's own tools or Chrome's, and Firebug's latest versions have issues under > PaleMoon. > > This is why I posted here, to hopefully get some clarity on the specifics > of Firebug's future and encourage the devs to work to make the latest > version of Firebug (PLEASE) to work in PaleMoon. > > Thanks for your reply! > > [deleted/re-posted to correct stupid typos] > > On Sunday, August 23, 2015 at 8:10:40 PM UTC-7, San wrote: >> >> They've already said here (if I understand correctly) that the future >> Firebug will be built on top of Firefox's own developer tools, rather than >> being a completely independent extension. I don't know whether I'll like >> the new Firebug or not, but I'm pretty sure it will continue to exist in >> some form. >> >> I'm not so sanguine about all the other web-devel extensions I use in >> Firefox, however. I find it hard to believe that all those extension >> developers, almost none of whom have been paid a dime for all their hard >> work, will just accept having to throw out all their code and start all >> over again. I suspect that most of the power extensions for Firefox-based >> devel will cease to exist, and with it my main reason for using Firefox at >> all. >> >> Also, the Chrome extension environment, which Mozilla will apparently be >> adopting (just as they've adopted Chrome's simplified interface, for the >> most part) doesn't allow an extension to get down into the guts of the >> browser and make major changes. For example, look at the awkward interface >> that Chris Pederick was forced to use in Chrome for his great Web Developer >> Toolbar, compared to the much more elegant interface that the same >> extension has in Firefox. I expect nasty changes like that throughout -- in >> the name of "security" Firefox will be less configurable than before -- the >> main characteristic distinguishing it from other browsers in the first >> place. >> >> Already, FF is alerting (in both Mac and Windows) that ColorZilla is "not >> verified for use in Firefox," despite its claiming to be signed (and no >> response from the developer to inquiries). I think Firebug is probably the >> one devel extension that I'm fairly confident *will* continue to work -- >> but will it be as good, or hobbled by all Mozilla's new restrictions? And >> will Firebug alone be a sufficient reason to stick around? >> >> On Sat, Aug 22, 2015 at 4:43 PM, William Nerini <wne...@gmail.com> wrote: >> >>> Given that, according to this post >>> <https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/>, >>> >>> it appears plugins that currently rely on the Add-on SDK will stop >>> functioning, as well as plugins using XUL, XBL and XPCOM. How will this >>> impact Firebug? I've looked, briefly at the Firebug.next project, but it's >>> not clear that's a response to these announced changes. >>> >>> At this time, Firebug is, literally, the *only *reason I still use >>> Firefox, and is irreplaceable in my development process; no other browser >>> had a tool remotely approaching Firebug's power and flexibility. So I'm >>> hoping to get some clarity on where you folks are, given the announced >>> changes. >>> >>> Thanks, >>> Will >>> >>> -- >>> 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 http://groups.google.com/group/firebug. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/firebug/6277c77a-934a-4fd0-8fcf-833b0dc0fd5b%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/firebug/6277c77a-934a-4fd0-8fcf-833b0dc0fd5b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Lawrence San >> Business Writing: Santhology.com >> Cartoon Stories for Thoughtful People: Sanstudio.com >> >> -- 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 http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/4ae7eb0a-860c-4b40-86b0-d871388b9c4d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
