3 ms·
It's still needed in many cases. For instance, I wrote an IndexedDB-heavy web app. It doesn't work in browsers that don't support IndexedDB. So I do feature de
by streptomycin 13y ago
It's still needed in many cases.
For instance, I wrote an IndexedDB-heavy web app. It doesn't work in browsers that don't support IndexedDB. So I do feature detection and if IndexedDB is not supported, I show an error message telling the user that if they want to run the app, they have to use a more modern browser like Firefox, Chrome or IE10.
...except on iDevices, where it is literally impossible to install any browser that supports IndexedDB, despite the fact that it is possible to install something called "Google Chrome" that is not really Google Chrome. So I do user agent detection to display a different message to those users, so as to not give them false hope and confusion.
- Touche 13y agoYou can use a polyfill that falls back to WebSQL (Supported on iOS): http://nparashuram.com/IndexedDBShim/ http://nparashuram.com/IndexedDBShim/
- streptomycin 13y agoI tried that and couldn't get it to work. Seems I'm not the only one with problems https://github.com/axemclion/IndexedDBShim/issues https://github.com/axemclion/IndexedDBShim/issues Admittedly I could invest more time to try to get it working, but iOS represents a relatively small fraction of my users and even a working shim could have problems (IIRC there are serious bugs with WebSQL in iOS 7, not sure if they've been fixed; also, I don't know what this shim approach would do to performance in an IndexedDB-heavy app).