> You don't. Firebug 2.0.7 is even working in Firefox 38.0 in case e10s is > disabled. > > The statement in teh linked page for e10S is, "The e10s team estimates >> e10s with a single content process will be enabled in Firefox Release by >> the end of 2015" Well we are in January. I cannot find anywhere that >> states, "version x of firefox will have the e10s enabled". The one site I >> did find mentions the tag "browser.tabs.remote.autostart" which is set to >> false, yet the 2.0.7 will not work. >> > > Please start another thread as this one gets quite lengthy and it's hard > to track such issues individually. > > Sebastian >
Firebug 2.0.7 is very buggy in 37 and up. Almost every single time Script or Network console was open and a JSON post was done and data was retrieved and the UX was inserted the whole TAB would freeze. Nothing in the tab would work. No HTML could be interacted with (though it did get updated). Even the Browser's UX was unresponsive in that you could click in UI Elements (address bar) but nothing would happen. in almost all cases you could not hit F5/Control+F5/Control+R to reload. One had to close the tab. I'm generally not fond being peed upon and calling it a warm spring rain. Call a spade a spaid. The Web Developer tools in Firefox have been ARound for a good while. God knows I said "yes" to their installation of them about 5(?) years ago. And they are exactly as utterly useless today as they were 5 years ago. Not in the same state as they were but still it's like driving a car that has 4 wheels but is missing one of the wheels, the steering wheel, the driver seat, the lever to the pedal and the windshield. Sort of like hey you took 4th place at Olympics, but nobody talks about 2nd or 3rd place at the Olympics let alone 4th place let alone the people who got there. Do the best that you can, be the best, be first. *The ex-Firebug team did an awesome job. They went to the Olympics, They took first place and took home gold. * The new FWG team knows more about closing tickets with canned responses such as (Submit a ticket) and have somebody else close the ticket with a canned response (this would be duplicating features) when it in fact is not. They more or less carry very similar stances and arguments as the team that decided that they would change the Firefox Search Engine and hide the icon, and make it as painful as possible to switch the default search engine and refuse to talk about Transparency and User Feedback. Which arguably is probably the reason why Firefox is back where it was 10 years ago, back where it was 20 years ago when it lived under a different banner/name (10-26% market share). But that's completely and utterly unrelated and off topic. -- 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 [email protected]. To post to this group, send email to [email protected]. 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/8015d71d-12cf-4a00-96d5-49d480a58379%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
