[kinto] Migrate browser.storage.local to use kinto collections

ASSIGNED
Assigned to

Status

()

Toolkit
WebExtensions: Untriaged
P3
normal
ASSIGNED
11 months ago
19 days ago

People

(Reporter: bsilverberg, Assigned: glasserc)

Tracking

(Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [storage]triaged)

(Reporter)

Description

11 months ago
This was discussed in bug 1253740. storage.sync is going to use Kinto collections to store data locally, and this could also be used for storage.local. Sharing this implementation will result in simpler code for storage in general.

In addition to changing the implementation of storage.local to use Kinto, this bug also needs to include a facility that will automatically migrate any data currently stored in storage.local's json files to Kinto collections.
(Reporter)

Updated

11 months ago
Assignee: nobody → eglassercamp
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Migrate browser.storage.local to use Kinto collections → [kinto] Migrate browser.storage.local to use kinto collections
Whiteboard: [storage]triaged
(Assignee)

Updated

6 months ago
Blocks: 1311710
No longer blocks: 1253740

Updated

26 days ago
webextensions: --- → ?

Updated

26 days ago
webextensions: ? → ---

Comment 1

19 days ago
Does this mean that storage.local entries will be separate records? I am working on data migration for Adblock Plus and was horrified to discover that all data in storage.local is being saved as a single JSON blob - for my Adblock Plus config that's currently 26 MB, and only part of that data really needs to be loaded every time.
Blocks: 1226547
You need to log in before you can comment on or make changes to this bug.