New issue
Advanced search Search tips

Issue 916467 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Ability to save the Local Storage and IndexedDB contents to a file

Reported by xvi...@gmail.com, Dec 19

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce the problem:
Currently there is no option for easy export of the Local Storage or IndexedDB contents. You either require to read leveldb from the Chrome directory, or patch Chromium code.

What is the expected behavior?
It would be nice to have the ability to save the contents of Local Storage and IndexedDB:
1. Per site (in case of Local Storage) or per database/storage (in case of IndexedDB)
2. Per object - to be able to save some value.
3. Format? I don't know, using JSON probably is the easiest way to do that.
4. The most logical way is to add the feature in the righ-click context menu for the objects and storages.

What went wrong?
Missing feature to export the Local Storage/IndexedDB

Did this work before? No 

Chrome version: any  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
It might make sense to add "Export" into the context menu for origins listed in devtools/Application tab.
Clicking it could e.g. download a json file or at least dump the json into the console so the users can copypaste it.

Even though it's pretty trivial to export localStorage via copy(JSON.stringify(localStorage, null, '  ')), it's much harder to automate IndexedDB export this way after Chrome 60 removed webkitGetDatabaseNames in  bug 696010  and requires running quite an intricate hack inside devtools-on-devtools or use the debugging protocol in an extension via chrome.debugger API.
Labels: Needs-Milestone
Cc: hhli@chromium.org
Status: Assigned (was: Unconfirmed)

Sign in to add a comment