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

Issue 684107 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Feature



Sign in to add a comment

DevTools: console access for response json

Reported by rro...@zenefits.com, Jan 23 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36

Steps to reproduce the problem:
1. 
2. 
3. 

What is the expected behavior?

What went wrong?
would be cool to do a `== $0` style console-accessible variable for network responses, esp. json. can clarify further if needed.

Did this work before? N/A 

Chrome version: 55.0.2883.95  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 24.0 r0
 
Labels: -Type-Bug Needs-Milestone OS-Linux OS-Windows Type-Feature
Status: Untriaged (was: Unconfirmed)
Thanks for the report.

Considering this as feature request, marking as Untriaged and requesting Dev team to provide update.
Owner: l...@chromium.org

Comment 3 by l...@chromium.org, Jan 30 2017

Cc: l...@chromium.org
Owner: allada@chromium.org
Status: Assigned (was: Untriaged)
Summary: DevTools: console access for response json (was: feature req: console access for response json)
Thank you for the request.  Further clarification about your use case and how your current workflow is, would be welcome.

$0, currently used for the selected element, isn't super intuitive to me.  Logged console objects have 'save as global variable' on right click, but for copying json data, wouldn't right click > copy/paste into the console do the same?  Please let us know about how your workflow might improve.

Comment 4 by allada@chromium.org, Jan 30 2017

Labels: -Pri-2 Pri-3
Status: WontFix (was: Assigned)
This would be a cool feature, however there's already a decent workaround of:

1) Open network response
2) Select all -> copy
3) Paste into console + assign to variable.

The process is not very elegant, but this is already a corner case. This would also be a bit tricky to implement since Network can only open network requests on selection and we only ask blink for the resource data if the user asks for it and to top it all off, it is possible for blink to purge the network request data even if devtools is open, and we'd have a hard time showing this happened if a user was trying to access the data with a $0 like command.

Thank you very much for the suggestion, but I think it might be a more useful to figure out a way to handle this without requiring console.

Thanks again!

Sign in to add a comment