New issue
Advanced search Search tips

Issue 914825 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

When copying a response from the network tab of google chrome that was sent in base 64, it copies the decoded message

Reported by ryan.hir...@gmail.com, Dec 13

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Open Developer tools and go to the network tab.
2. Make a request for an object that will be returned in base64.
3. Right click on the request and choose "Copy -> Response"
4. Paste that into the text file. The file is the decoded message.

What is the expected behavior?
The document should be copied as a base64 item

What went wrong?
The file is not copied as base64, but rather the decoded file

Did this work before? Yes 70

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

Change occured between 70 & 71 (tested on 2 devices for confirmation)
 
Components: -Platform>DevTools Platform>DevTools>Network
Owner: jarhar@chromium.org
Labels: Needs-Triage-M71 Needs-Bisect
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue...

Tried to reproduce the issue on reported chrome version 71.0.3578.98 using Windows 10. Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome 
2. Opened Dev tools > Network > refreshed the page and observed requests on network tab
3. Right clicked on request and copied the request from Copy - Response
As we have observed that the page copied 

@Reporter: Could you please check the attached screencast and let us know if we missed anything from our end and if possible provide a screencast/screenshot of expected behavior. 

Thanks.!
914825.mp4
6.8 MB View Download
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment