Strange design decision when exploring http requests

[Ventsyslav Vassilev]

Well, maybe this is my fault or i simply struggle to find this out in the 3.0.0, but can you explain me the following:


With 2.0.6 we have the very useful interface to inspect/debug Ajax calls from a particular page.
Directly within the Firebug's Console tab we are able to see the request/responce headers, params and responce body and even the formatted JSON responces in a very handy way, just like this:

All this directly via the Console tab - for me it is a priceless functionality.

Now, with 3.0.0 it seems impossible and we are forced to switch to the Network tab, only to see all this in the far right.

When you click on the appropriate request within the console tab, you end up with something completely unusable in a pop-up window:

To be honest, i can not understand this - no well formated params, no human readable JSON responce - in fact - this are the normal FF developer tools.

Who needs this change?
In the blog you say the purpose of the 3.x is to complement FF's developers tools with a missing functionality.
Instead - i can see the lack of the most useful feature (personally to me, of course)
Will be glad to see it right back, if possible

[Jan Honza Odvarko]

> Will be glad to see it right back, if possible

Yes, this will be again available in FB3.

You might want to follow these reports:
https://github.com/firebug/firebug.next/issues/180
https://github.com/firebug/firebug.next/issues/181

Honza

[Ventsyslav Vassilev]

Yes!
Great to see i'm not the only reported that.
Thanks Jan, keep the good job.

[Dan Vladescu]

I was about report the same issue, I do agree to this comment and waiting for the implementation. Thanks