Issue 822711 link

Starred by 1 user

Issue metadata

Status:	WontFix
Owner:	█ eostroukhov@chromium.org Last visit > 30 days ago
Closed:	Sep 7
Components:	Platform>DevTools
EstimatedDays:	----
NextAction:	----
OS:	Mac
Pri:	2
Type:	Bug
Needs-Feedback Via-Wizard-DeveloperTools Triaged-ET Needs-Triage-M65

Session or local storage inspector does not display key/value combination

Reported by john.gin...@gmail.com, Mar 16 2018

Issue description

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

Steps to reproduce the problem:
1. Open a website that stores data in local or session data
2. In developer tools, click Application > Storage > Local Storage or Session Storage
3. Instead of key/value pairs, only a single string value is displayed

What is the expected behavior?
I expect to see a set of key/value pairs

What went wrong?
Key/value pairs have been replaced by a single string with no indication of what key it relates to. This doesn't appear to be preventing websites from working, but it does hinder development where you need to inspect values.

Did this work before? N/A 

Chrome version: 65.0.3325.162  Channel: stable
OS Version: OS X 10.13.3
Flash Version:

Comment 1 by john.gin...@gmail.com, Mar 16 2018

I found the issue. The key/value pairs were not showing by default until I dragged the line below the Key/Value headers down. For some reason they were hidden after the recent upgrade.

Comment 2 by krajshree@chromium.org, Mar 19 2018

Labels: Needs-Triage-M65

Comment 3 by viswa.karala@chromium.org, Mar 19 2018

Labels: Triaged-ET Needs-Feedback

Tested the issue on chrome reported version 65.0.3325.162 using Mac 10.13.3 with steps mentioned below:
1) Launched chrome reported version and navigated to amazon.com
2) Opened Devtools > Application > Storage > Local Storage, Able to see Key and Value sections under local storage

@Reporter: Please find the attached screen shot for your reference and let us know if we missed anything checking the issue, provide your feedback on it which helps in further triaging it.

Thanks!