Switch to ironDB?

[eight04]

There are many users got data loss bug due to browser bugs (#278, #528) that we can't fix them in the extension. @vsemozhetbyt has suggested an ironDB library which can push data into multiple browser storage just like what tophf tried to do.

I'm not sure if it is a good idea though. It is basically duplicating the data.

[Mottie]

There's no guarantee that ironDB will solve this issue. It also tries to save the DB to a cookie, which is impractical for our case, since a cookie can only store 4093 bytes.

I think the next best solution would be to add popups (with an option to disable) that remind the users to backup their styles.

[tophf]

If we decide to switch to something, we can switch to chrome.storage by default and offer an option to use IndexedDB for those who wants speed.

The slowness of chrome.storage shouldn't be a big issue: it's observable only when all styles are retrieved from the storage at startup so instead of say 40ms it would be 150ms for a 6MB worth of styles. Could be worse though on a slower computer. But then we use a cache. Updates of individual styles are fast in both chrome.storage and IndexedDB.