IndexedDB should probably allow me to specify whether a site can store info between sessions. Right now IDB seems to be a supercookie. Even if I specify a site should only remember cookies for this session, IDB data appears to persist.

Oh. That applies to other modes as well. It should be possible to set a preference to request a prompt for the initial 5MiB of IDB data, or to disable IDB. Pretty much the stuff I'm used to doing w/ cookies. This is probably related to bug #781984 since IndexedDB also seems to ignore: Preferences->Advanced->Network->Tell me when a website asks to store data for offline use. Perhaps it should be duped against it come to think of it.

OMG, almost 3 years old and still the easiest way to bypass user control. Meanwhile I seriously ask myself, why do I even bother about cookie storage in the first place if it is so easy to store the Cookie info with other APIs that bypass all user control?

Isn't this bug a duplicate of, or at least strongly related to, bug 1047098?

This bug is about the fact, that IndexedDB is stored persistent for a domain, even though Cookie storage for that domain is limited to current session only. Bug 1047098 is about IndexedDB not getting cleared when the user explicitly requssts data to be cleared, which would clear all data, even data form domains that are allowed to store data persistent. I don't know where the correlation should be. Even if that bug is fixed, it doesn't mean that a manual cache clean up will delete all data of all domains and even if bug 1047098 is fixed, it doesn't mean that the browser will now respect the "session only" setting.