> > On Tuesday, January 27, 2015 at 5:23:58 PM UTC+1, Richard Muse wrote: >> > On Monday, January 26, 2015 at 5:03:42 PM UTC-5, Sebastian Zartner wrote: >>> >>> Hi, >>> >>> Note that for Firebug 2.0.7 you need to have e10s >>> <https://www.google.com/url?q=https%3A%2F%2Fwiki.mozilla.org%2FElectrolysis&sa=D&sntz=1&usg=AFQjCNG8t8sJZzH3ci8i5zma8Zl-KVGB5Q> >>> >>> disabled. >>> >> Nice to say, but there is no option I see to disable it in the general >> configuration screen your link points to. (I had checked this before.) When >> I do a abount:config there is an option for print.enable_e10s_testing which >> is defaulted to true. Is that what you may be referring to? >> > > My fault. Firefox 36 doesn't have e10s enabled by default. You can easily > see whether e10s is enabled. When the browser tab texts are underlined, it > is enabled. In Nightly (38) *Enable E10S (multi-process)* is the first > option you see when you open the browser options. > I have Beta 36. As mentioned by Constrained Serenity, we see a complete FireFox lock up when 2.0.7 is installed. The other people in the office that were beta tracking went back to 35 in order to keep using FireBug. The tabs are not underlined and I see no where to turn e10s off, so I am still stuck there. I have attached the option screen shot (trimmed down) where you can see e10s is not an option.
> Did you try out the *Network* panel? It shows the data inline, displays >>> the response body and POST parameters as expected and also parses JSON. >>> I just created bug 1125985 >>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1125985> to link the >>> console entries with the *Network* panel instead of opening the popup >>> window. >>> >> Yes, I checked the network panel. While it is easier to see the >> information on the right side panel, it is a HUGE amount of spam where it >> used to just show my request in the console >> > > Which 'spam' is that? > The spam of all the image and js requests. As a fully web app, we have a lot of images and various js pages that get loaded depending on the page and where the user is. Opening the main page gives me about 3 pages of network panel requests. the ones I wanted were in there when I started going line by line. I did see what every request was appearing twice. Not sure why that is. Your example was only in there once, but all the ones from our site are appearing twice, once as a zero KB and the same time as the real request. So having every entry twice did not help my spam problem. :) Will have to look into why we get double requests... So linking back the real requests where we can use the console would solve the issue for the most part. As I just figured out, I can filter to XHR to get just the requests, so that helps as well. Amazing what might be there when the "easy" path suddenly gets ripped out from under you. So not to say they are the same, but this is feeling a something like changing Windows versions. Part of the trouble is figuring out where what you need has been moved. > not only that, but the JSON panel does NOT parse out the nice pretty json >> such as the earlier firebug did. It is just a long string. >> > > It works fine for me on this test case: > http://www.softwareishard.com/firebug/tests/1275/Issue1275.htm > Ok, I see the problem I was having was the duplicated entries I mentioned before. It made it appear to "fail" to show results until I figured out which were the real entries and which the false ones. Then I saw the parsed results. So I can retract this one. > That is fine, but looks like someone's timing is really off since I HAVE >> to use FireBug 3 to have anything work with FireFox 36.0. >> > > You don't. Firebug 2.0.7 is even working in Firefox 38.0 in case e10s is > disabled. > As mentioned by myself and Constrained Serenity, it is not working. It just locks completely up. Open FireBug 2.0.7, cannot click anything, close it, page acts as normal. Latest Beta of 36 being used. > Sebastian > Richard -- 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/9e68dcd9-18f7-4676-adb4-e8e66560e80b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
