Open Bug 1515293 Opened 6 years ago Updated 2 years ago

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

Categories

(DevTools :: Storage Inspector, enhancement, P3)

66 Branch
enhancement

Tracking

(Not tracked)

People

(Reporter: anton.kochkov, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 Steps to reproduce: Currently there is no option for easy export of the Local Storage or IndexedDB contents. You either require to read database from the Firefox profile directory, or patch Firefox code. Actual results: Missing feature to export the Local Storage/IndexedDB Expected results: 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.
Marking this as an enhancement for now so developers can take a look at it. Thanks for your suggestion
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: Untriaged → DOM: Web Storage
Ever confirmed: true
Product: Firefox → Core
Priority: -- → P5
Moving this to devtools storage inspector as I think that what's intended from expected results step 4.
Component: DOM: Web Storage → Storage Inspector
Priority: P5 → --
Product: Core → DevTools
Has STR: --- → yes
OS: Unspecified → All
Priority: -- → P3
Hardware: Unspecified → All

This issue sounds similar to bug 1062613. There are two things that distinct them, though:

  1. This one also refers to the IndexedDB, for which exporting data might work differently than for the local or session storage.
  2. The other bug mentions exporting to the clipboard besides to a file.

If exporting could work the same for all the storage types (code-wise), I suggest to focus this one on exporting to a file and bug 1062613 on exporting to the clipboard. If exporting needs to be handled differently per type, this one should focus on IndexedDB and the other one on local and session storage. Then they'd probably restrict export to a file and we'd need to create a new bug to handle exporting the data to the clipboard.

Belén, what's your opinion on this?

Sebastian

Flags: needinfo?(balbeza)
See Also: → 1062613

Thanks Sebastian, I think indexedDB would need some custom code to handle the export of the whole database vs a single table, so I rather keep them as separate bugs.

Flags: needinfo?(balbeza)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.