3 ms·

How can I revert it back? We had a major incident, I started Firefox to debug, of course it updated upon start, and replaced Firebug with this shit. Then Firefo

by frik 10y ago

How can I revert it back? We had a major incident, I started Firefox to debug, of course it updated upon start, and replaced Firebug with this shit. Then Firefox crashed while I tried to click on the bubble which advertised to switch back. After the restart of Firefox there is no way to change back!? Stupid autoupdate crap, who in the right mind thought a feature incomplete tools is good to be forced upon users. Allow me to change back to Firebug, or Firefox is dead for me (until Servo replaces it).

Steeeve 10y ago
I ran into the same exact scenario. I tried to get moving with the devtools and while it looks similar and breakpoints seem to work better, getting acclimated was wasted time that I would rather have spent after the production issue was resolved. That being said, I can't fault Mozilla for this. I've known for some time that Firebug was on it's way out.
erikb 10y ago
A good question. But I guess people downvote it since this is not the correct platform for this kind of question.
frik 10y ago
The points are: * Force it upon user * Advertising "revert back", which restarts Firefox but Firefox crashes and after another restart forgets its settings - no one tested that option * Firebug theme is just a theme, and several features and functionality found in default Firebug are still missing in their DevTools. The usability is different, especially in the AJAX/console tab. And where is a proper DOM tab? * worst thing, it happened during a major incident, I login in remotely to my workstation just to find out my Tool changed under my feet completely, with all prior knowledge useless. I had to use Chrome DevTools which has more features, but even it lacks features as mentioned above - Firebug was the most matured Tool after all. * Firefox still hasn't proper multi-process support, if you understand multi more than two processes. It's a far cry from what IE8+ and Chrome offer.

by frik 10y ago

Steeeve 10y ago

I ran into the same exact scenario. I tried to get moving with the devtools and while it looks similar and breakpoints seem to work better, getting acclimated was wasted time that I would rather have spent after the production issue was resolved. That being said, I can't fault Mozilla for this. I've known for some time that Firebug was on it's way out.

erikb 10y ago

A good question. But I guess people downvote it since this is not the correct platform for this kind of question.

frik 10y ago

The points are: * Force it upon user * Advertising "revert back", which restarts Firefox but Firefox crashes and after another restart forgets its settings - no one tested that option * Firebug theme is just a theme, and several features and functionality found in default Firebug are still missing in their DevTools. The usability is different, especially in the AJAX/console tab. And where is a proper DOM tab? * worst thing, it happened during a major incident, I login in remotely to my workstation just to find out my Tool changed under my feet completely, with all prior knowledge useless. I had to use Chrome DevTools which has more features, but even it lacks features as mentioned above - Firebug was the most matured Tool after all. * Firefox still hasn't proper multi-process support, if you understand multi more than two processes. It's a far cry from what IE8+ and Chrome offer.