blog-indexeddb-safari-leaks-demo VS localForage

One benefit that immediately comes to mind is the ability to protect yourself against a major security flaw in Safari:

https://safarileaks.com/

Apple did issue a fix after a few weeks but with no alternative browser engines the only alternative was “don’t use the web on your iPhone”, which is absurd.

Other user benefits might include better performance, more capabilities (it took Apple years to implement WebRTC, for example) and in general more competition that might spur Safari into becoming a better browser.

Assuming it's not straight up broken once again, like when localStorage was bugged and browser data would get lost last year or when indexedDb was broken und would leak data.

see: https://safarileaks.com/

I researched the Safari vulnerability, and yes, this appears to only affect iOS 15 devices. The message on https://safarileaks.com/ states "Your browser is not affected. Please open this demo in..... any any browser on iOS and iPadOS 15." Good to know!

Are you talking about this? Apple fixed it about a week ago with the release of macOS 12.2.

In the past, there were a few (though rare) cases where Apple has even patched unsupported versions. It probably depends on how easy it is for them. But for the most recent problems, like this and that, there are no fixes beyond Catalina.

Safari is a dumpster fire right now.

safarileaks.com security vulnerability fixed in Safari 15.3

The IndexedDB issues. Fixing things takes times, but it's crazy that's its taken 2 months even for a response

Not really an answer but have you looked into https://github.com/localForage/localForage

I may not be pointing you in the right direction but, please read about [IndexDB storage](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB\_API) method and packages like [localForage](https://localforage.github.io/localForage/) that use it under the hood.

LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.

Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.

I find localForage is pretty helpful for this stuff https://github.com/localForage/localForage

localForage (https://localforage.github.io/localForage/) mirrors localStorage syntax, but uses IndexedDB in the background. If that's not supported, it uses WebSQL and then LocalStorage

This is why we have localForage.