Firefox 111.0 enabled Origin private file system access

Re:Firefox 111.0 enabled Origin private file system access by postdb on Wednesday March 15, 2023 @08:16AM (#35167090)

> Worst part was, a few months after I made the app, Chrome dropped a bug on an update that wiped local storage on update, so I lost months of IndexedDB records.

That is the state of web currently. I don't care if FAANG or some standard committee have RFC saying that the storage is persistent, if it is NOT a file on the system it can just go away much like cookies or cache. Just think of what Safari did to indexdb of sites that is NOT bookmarked on the screen.

[ Parent | on HN ]

Re:Firefox 111.0 enabled Origin private file system access by AshleysBrain on Wednesday March 15, 2023 @08:44AM (#35167426)

Saving user's work to IndexedDB turned in to a real problem for us for a similar reason: sometimes users go in to their browser settings and click an option with wording like "clear cookies", and then it also wipes IndexedDB and all their saved work. I don't know if that applies to OPFS, but saving to the real file system (rather than just OPFS) seems a lot safer, and also integrates well with other tools, like backup software.

I've also long felt that "cookies" is a really poor term - these days it really refers to "storage on your local device accessed by websites", and the confusion literally leads to data loss.

[ Parent | on HN ]

Re:Firefox 111.0 enabled Origin private file system access by bagacrap on Wednesday March 15, 2023 @10:00AM (#35168452)

In Chrome the wording is "cookies and other site data".

[ Parent | on HN ]