And it's not only wired. I've come across a lot of internal sites and intranets that are poorly tested on anything but Chrome. I know, it's not exactly the same thing as the old IE/ActiveX but it still grinds my gears when it happens.
Makes total sense as an engineering tradeoff if you're not in the business of saving the web but publishing a magazine.
We've been pushing this since IE6 ruled. :-)
Cross browser compability should be easier than ever so it should just be a matter of being a professional developer.
But I think this thread started with a CMS that didn't even work except in Chrome.
The w3c requires a standard to have 2 or more independent implementations of a spec. Why should Mozilla or Microsoft be responsible for writing an independent implementation of SQLite just so webSQL can be a standard.
Or, if you committed to keeping it simple and not chasing Postgres and MySQL, then there’s kinda no point. Just write a little SQL wrapper around LocalStorage.
In the end, that’s why we have LocalStorage—it’s simple. Like a file system. It means that you can have a clear sense of what browsers do and do not support.
I guess here’s a direct question: why do you prefer WebSQL over a tiny JS library that does the same thing?