Add a Request Tab to Network Developer Tool
Reported by
tyler.br...@gmail.com,
Apr 26 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: 1. Open Developer Tolls 2. Select "Network" panel. 3. Make request 4. Observe that request headers + payload information is found in "Header" tab (instead of a request tab). What is the expected behavior? As a developer I expect there to be a "Request" tab that is an analog to the existing "Response" tab containing the request payload data instead of finding "Request Payload" at the end of the "Headers" tab data. In addition I'd propose removing the "Headers" tab entirely in favor of having a "Request" and "Response" tabs each having a Headers/Payload section. Conflating the request headers, the response headers as well as the request body into a tab called "Headers" in the network panel doesn't make sense. What went wrong? This portion of the developer tools Network panel was designed in a way that doesn't match how developers look at the request/response cycle. Everything else is fantastic but I find myself teaching others about where to find the request payload and being baffled every time I describe it that this information is found in the "Headers" tab of the Network panel. Did this work before? No Chrome version: 58.0.3029.81 Channel: stable OS Version: OS X 10.12.4 Flash Version:
,
Apr 27 2017
Able to reproduce this issue on Mac 10.12.4, Win-10 and Ubuntu 14.04 using chrome reported version #58.0.3029.81 and latest canary #60.0.3081.6 . This is a non-regression issue as it is observed from M30 old builds. This seems to be a feature request. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Apr 28 2017
,
Apr 28 2017
This is not easy to solve. No matter which route we go down we will never make everyone happy. In the past (and arguably still today) it is much more common to have the entire request payload to be just headers with little to no content. Showing the payload under headers, yes, is a bit confusing, but since the payload is most frequently small, it does not seem like a great idea to have the payload have it's own tab. If we move the request headers and payload to a "Request" tab, it will regress many people's workflow because we believe most developers would like to see the request and response headers all in the same place. There's no one-size-fits-all solution to this UI problem and UI problems are the hardest challenge we have here on the devtools team. I'll discuss it with +chowse (our UI/UX expert) and see if he has any ideas.
,
Apr 28 2017
,
Apr 29 2017
It would be fine to keep the headers for both request and response under the headers tab but also have a request tab that only has the request payload.
,
Dec 14 2017
Closing as WontFix due to lack priority / resources. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kavvaru@chromium.org
, Apr 26 2017