Feature Request: Reorganize the tabs under 'Network' when viewing a request

[Blue Raja]

Currently, the organization of the tabs for a request/response looks like this:

"Headers"
↳ General
↳ Response Headers
  ↳ "View Source" = Raw Headers
↳ Request Headers
  ↳ "View Source" = Raw Headers
↳ Query String Parameters
  ↳ "View Source" = Raw QSP
↳ Request Payload
  ↳ (Preview of request)
 
"Preview"
↳ (Preview of response only)

"Response"

↳ (Raw response only)

This is, to be frank, a mess.  "Headers" contains lots of things unrelated to headers, for both the request and the response.  There are two tabs dedicated to the response (neither of which contain the response headers), and 0 dedicated to the request.  The response body is the only thing where viewing the raw data requires going to another tab, rather than clicking "View Source".

A better organization would look like this:

"Request"
↳ General
↳ Query String Parameters
  ↳ "View Source" = Raw QSP
↳ Headers
  ↳ "View Source" = Raw Headers
↳ Payload
  ↳ "View Source" = Raw Payload

"Response"
↳ Headers
  ↳ "View Source" = Raw Headers
↳ Payload
  ↳ "View Source" = Raw Payload

[Blue Raja]

Also posted at https://bugs.chromium.org/p/chromium/issues/detail?id=1070383

[Piotr Dobrogost]

"This is, to be frank, a mess.  "Headers" contains lots of things unrelated to headers, for both the request and the response.  There are two tabs dedicated to the response (neither of which contain the response headers), and 0 dedicated to the request.  The response body is the only thing where viewing the raw data requires going to another tab, rather than clicking "View Source"."

I completely agree with the above and has been always wondering why is it arranged in such illogical way?

Could somebody please provide any information why is it this way?

With the amount of changes in devtools in each release of chrome it's astonishing this has not changed over the years.

[Piotr Dobrogost]

Could we please have any feedback on this?

[Piotr Dobrogost]