Images tend to disappear once you've added several
Closed this issue · 2 comments
Due to the way IndexedDB tries to prevent websites from filling one's hard disk with binary data, it may sometimes occur that images get removed without any user interaction.
For this reason it would be better to store the image location and metadata in Local Storage instead and have a reference to the image blob in IndexedDB. This allows the user to restore the image again later on should IndexedDB decide to remove an image.
An investigation should be made to see whether it is possible to receive a notification or some indication on when and why an image gets removed as usually this should require an IndexedDB instance that takes up a decent percentage of the disk storage space (based on the documentation, at least).
This was partially fixed with the request for permanent storage to the browser. I haven't encountered any such issues for a while, but it's too soon to say this really fixed the issue.
I think it has been long enough with any reports of this happening, so I think it's safe to close this issue now.