I am puzzled by comparing IndexDB pitching for stand-alone (e.g.) single-page HTML applications with the fact that the documentation seems to indicate that the browser can delete your local data at any time. "Also, keep in mind that browsers can destroy a database, for example, under the following conditions:"
It seems that the options are: a) intended only for stand-alone read-only applications, or b) just agree that from time to time some users of your offline application will be out of luck and lose all their work when the browser gets into the mood for deletion IndexedDB data.
My question is: is there any serious discussion of this problem anywhere or (better, but too much to hope) a serious offline read / write application that deals with the problem? My searches on this topic were fruitless. For example, this complete stand-alone todo application example allows you to never mention the problem - who wants to store even simple todo data in storage that the browser can destroy at any time, and it cannot be trivially copied?
source
share