Oh, wow. Thank you so much. I have been tediously trying to copy and paste everything I could think of to reset FF for the past hour(s). I have that setting set to enabled. I am so glad you posted before I lost everything and tried to put it back together again (which would have just caused the same issue again as long as I had remembered to change that setting.Guest wrote:This problem occurs if dom.indexedDB.enabled is set to false in Firefox 35. The session store doesn't work anymore either. Don't delete your profile or reset Firefox, just set dom.indexedDB.enabled = true. Unfortunately this also allows any website to store databases on your computer (and track you with that). The only solution now seems to remove write access to the <profile>/storage folder.
Not to mention that you saved me from going through it again on another computer thinking it was an individual corrupted profile rather than caused by that setting.
So, any chance I can now just use Windows system restore to go back to before updating to FF 35 and just not update to 35? Or does system restore leave my FF 35 update even though it occurred after the last restore point?
Thank you both for your help.