[leeoniya]

it's not at all useful. all you get is some stack-tace-like thing without any of what you actually want to see. like req/resp headers and body, params, inline json/html decoding based on response type. chrome lags here by a large margin.

[clarkm]

Just click the request from the console, and it takes you to the network tab where you can see the headers, response, etc.

[leeoniya]

to see the response body of a request in chrome:

1. Click request in console

2. Find and click request again in Net panel

3. Click Preview or Response tab

4. Click console again to return

and then...

5. Oh wait, want to see something in the headers

6. Rinse and repeat.

In FB:

1. Click request in console.

2. See raw response body right away, or click headers to see headers or json/html to see those rendered nicely.

3. bonus: view multiple json requests in same window

[magicalist]

It's actually more like

1. Click request in console

2. Click on the request that was just highlighted for you in the Net panel

3. See headers right away, or click Response to see raw response or Preview to see those rendered nicely

4. Click console again to return

and then...

5. Oh wait, want to see something in the headers

6. Go to the Net panel, still there for you

It's a different workflow and it's probably annoying to you since you're not used to it, but "it's not at all useful" is edging past hyperbolic. Personally I feel like a clumsy idiot when I go back to Firebug, even though I used to live in it and once knew every quirk. I think that's just the way of developer tools.