IndexedDB implementations in various browsers had their quirks, but by far the quirkiest (buggiest) was Safari. I remember working with their implementation for

IndexedDB implementations in various browsers had their quirks, but by far the quirkiest (buggiest) was Safari. I remember working with their implementation for our web app about 3/4 years ago, and their implementation was so utterly unpredictable and unstable, that even their error messages didn't make any sense. It was as if they'd asked a blithering idiot to do their implementation for them, and didn't check any of the work. Thankfully, I believe things are better now (i.e. they get the basics of storing data right at least), but looking at this gist, they've found alternative ways of irritating developers. In the past, it was IE that used to bug the heck out of me, but now Safari has well and truly left IE in the dust in terms of its ability to annoy and dumbfound developers.