New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 650775 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 707852
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Feature



Sign in to add a comment

A separate tab for the Request Payload

Reported by thorn.ma...@gmail.com, Sep 27 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
Open the 'Network' tab of the Dev Tools and click on any request that has payload.

What is the expected behavior?

What went wrong?
Now, the HTTP request payload can be found on the tab called 'Headers', which doesn't make any sense. Just like it's done for the response (which got even two separate tabs - 'Response' and 'Preview'), the request needs its own tab(s).

Did this work before? No 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 
Cc: allada@chromium.org
Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
Status: Available (was: Unconfirmed)
Cc: -allada@chromium.org
Owner: allada@chromium.org
Status: Assigned (was: Available)

Comment 3 by kayce@google.com, Oct 13 2016

Labels: DevTools-User-Facing

Comment 4 by allada@chromium.org, Jul 20 2017

Mergedinto: 707852
Status: Duplicate (was: Assigned)
Merging to put discussion on one bug.

Sign in to add a comment