Disabling IndexedDB breaks sites

[allo-]

IndexedDB seems to become more and more important for different websites, like e.g. GMail (https://github.com/allo-/firefox-profilemaker/issues/130#issuecomment-419700161) and needs a bigger warning and possibly another default value

[allo-]

localstorage probably has a similar problem, but we do not disable it by default. Disabling cookies completely will break many websites as well.

Is there a quantum firefox compatible addon, which clears cookies and different storages at exit to make them "session cookies"?
Maybe some "cookie" addons can help, as firefox' forget history function seems to clear all storage apis when removing cookies.

[allo-]

More and more reports are coming in, the default should probably be changed.

[tjbenator]

Figured out that this breaks the twitter.com login page too. It appears that once you login, IndexedDB can be re-enabled.

[allo-]

Twitter is complicated. Disabling (all) cookies even breaks reading tweets, because you get an infinite redirect loop.

I wonder if we should change the setting to "not disabled" in the default profile and maybe refer to some addons that deletes browser storages, that can be added in the addons section.

As Mozilla unified the storage cleanup APIs, there could even be "Cookie" cleaners, that work for IndexedDB / localstorage.

[allo-]

It seems, that Mozilla has removed the option to disable indexedDB and introduced some bugs when dom.indexedDB.enabled is set to false.
I close here now. Bug #166 can be used for discussing the alternatives.