Lovefield, a relational database for web apps, works cross-browser
github.com
github.com
I've made quite a bit of effort to make error reporting as intuitive as possible, but admittedly this always needs to be improved. But the community is pretty active and always around to help if there are problems. :)
Lesson: always test cross-browser before commiting to a js library
Always test cross-browser before commiting to a js library, after you have committed to it, and on every browser or js library update.
This is a MAJOR UX violation. If you were going to by a car and you were told that's how it works you'd never buy that make/model. We keep getting by on the ignorance of end-user. That's not a positive.
I'm not sure what the details of the answer is. But I do know that accepting the status quo is no longer acceptable. The first step to solving a problem is to admit you have one. Step 2 is to make sure you identify the right problem.
We have a problem, yes?
You can use it with in-memory (no persistence, .MEMORY), IndexDB (local persistence, .INDEX_DB), or Firebase Realtime Database (cloud persistence, .FIREBASE).
I thought we got over "you must run this browser to have the app work" stuff when we all got off IE6.
I understand the use case is to store the data locally, and I'm sure it has its use cases, but they are probably limited.
Assumption is flawed -- we haven't all gotten off IE6, it's use has simply dropped significantly. It's a simple case of diminishing returns, and it will never cease to exist, even with the rise of evergreen browsers. There's also a big difference between supported browsers and explicitly mandating certain browsers.
That said, IE10+ is somewhat limiting, but some people may be completely fine with that limitation. For about 90% of the apps I personally work on, IE10+ is perfectly acceptable.
I'm sure there's been updates since then, just linking for reference.