Bug 30483

Summary: Web Inspector: Always show the Local and Session Storage views
Product: WebKit Reporter: Timothy Hatcher <timothy>
Component: Web Inspector (Deprecated)Assignee: Brian Weinstein <bweinstein>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: aroben, bweinstein, joepeck, rik, robert.colburn+bugzilla, rtakacs
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 116924    
Attachments:
Description Flags
Always Show Datagrid none

Timothy Hatcher
Reported 2009-10-17 13:51:43 PDT
We should always show the local and session storage items in the Storage panel. They should also have an empty datagrid so you can insert new values from the UI without havign to poke it with the console first.
Attachments
Always Show Datagrid (38.40 KB, patch)
2009-10-29 11:02 PDT, Brian Weinstein 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Brian Weinstein
Comment 1 2009-10-29 00:49:31 PDT
This is tricky because they are not added into the Web Inspector until they are accessed (if a script calls localStorage, or someone types something in the Console, and it tries to autocomplete to localStorage. I am not sure the best way to solve this, but would be open to suggestions. One thing that should be more straightforward, and I will work on is showing an empty datagrid instead of a "This Storage is Empty" view, since local and session storage are now R/W from the inspector.
Brian Weinstein
Comment 2 2009-10-29 11:02:18 PDT
Created attachment 42113 [details] Always Show Datagrid
Brian Weinstein
Comment 3 2009-10-29 11:16:43 PDT
Part 1 landed in http://trac.webkit.org/changeset/50287.
Brian Weinstein
Comment 4 2009-10-29 11:17:06 PDT
Comment on attachment 42113 [details] Always Show Datagrid Landed, clearing review flag.
Rob Colburn
Comment 5 2012-06-11 10:03:42 PDT
Old bug. What's the status here Brian?
Roland Takacs
Comment 6 2013-05-29 00:50:56 PDT
It works correctly at me. I will close the bug if noone would mind.
Note You need to log in before you can comment on or make changes to this bug.