Hi The work that the firebug group does in creating — by far — the best debug tool for web development is exemplary and we all appreciate it.
But I could have written this post myself on behalf on my dev group and, I suspect, so could many developers. We use Firebug 2.07. There are real reasons we have avoided using the built-in FF tools and nearly all the tools in other browsers. Without going into unnecessary detail, suffice it say that the reasons are self-evident when viewed side by side. So, it is with increasing alarm that we are monitoring the convergence of FF dev tools and Firebug. The reasons for unifying a best-of-class utility and perhaps the worst are not clear to us, but it seems inevitable. With respect to the current post, we use firebug *exactly* this way (as do many folks) in an ajax based environment. We develop single page ajax web apps and the console-based ajax-http read-out is **critical** to us, not only for the headers (and other POST or GET parameters) but for the JSON returns as well. Note that we also use kendo widgets (as well as others) that employ a Data Source object that permits ajax fetching of parameters through its transport property. These widgets range from charts to dropdown to grids. It is critical to our dev work that we be able to see this interaction in context. Note finally that we also use many Deferred objects to sequence certain UI functions, especially page init functions. Many times a jQuery "parent” ajax call wraps these Deferreds which may embed a series of kendo-based ajax transport-based data fetches; the result is a series of server interactions that must be executed in sequence. All of this is required due to the anomalous nature of javascript threading. In debugging, we often drop console messages within these contexts to make sure the sequences execute correctly. The presence of the ajax-http console is indispensable here. My team has disabled the FF auto-update on the dev profiles since we are worried that that we will lose the tools we need here. Please do not compromise these and other features in the next version of this amazing tool. We have a theory that the folks at Google and Firefox (and Apple) who have developed the various browser-native tools are NOT web app developers and do not really understand the reasons that firebug is so effective - - and popular. Thanks S On Saturday, January 17, 2015, Richard Muse <[email protected]> wrote: > I was using the 2.0.7 but the beta version of Firefox. When I updated to FireFox beta 36 Firebug stopped working. I saw this was a chance to get it working and ensure that I tested the latest stuff before the other developers in the office got bitten by any issues. > Two quick things I see as massive steps back from our points of view. We are a heavily AJAX shop, so I am coming in from that perspective. This behavior may mimic the built in FirFox dev tools, but we did not use them for good reason. > Formerly from the console, the request would expand and show the headers, params and nicely parsed and formatted JSON when available. There are several problems that I see with the new interface. > - The viewing the request pops up in a window. The window goes to the top left monitor area, instead of staying where firebug is opened. Annoying. > - I turned on the response body, but it will not retrieve the whole thing, only a part until I click to retrieve the rest. > - Even after I retrieve it all, the JSON parsing window is gone, which means I have to copy it from the window into another editor and format there. > The response no longer is nicely formatted either. The response body is big long string of params. When you are running online application with anywhere from 3 to 50 posting params this again is a PITA to read. > Just those two general items made FireBug a MUST for our development shop. The Alpha for 3 is so far harder to use (in our case) than Chrome's dev tools. At least I do not have to request the rest of my data manually every time I make a query, after moving the pop up window back over to the proper monitor and sizing it so I can see more than a few lines. > I find it disappointing that a decision was made to "merge" the two tools in FireFox and apparently the builtin tools take precedence. Firebug was far better almost across the board. Hears to hoping it can regain that former usefulness before version 3 is required by the general audience and not just those on beta tracks. > I understand I am on beta and alpha tracks. I am not screaming, yet. A few months of not having a "useful" firebug might do it to me though. ;) > But for now, mostly Chrome it is. > > On Monday, November 10, 2014 at 9:31:18 AM UTC-5, Jan Honza Odvarko wrote: >> >> http://bit.ly/1wKR16L >> >> Honza > > -- > 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/6ae16e75-4b05-4f7a-8a90-181428beed5d%40googlegroups.com . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAEvNn2oEOwB89HVZyfGN6mj5vA3tcKKcXhdSGa6KNAD1HUQrnw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
