Why don't my add-ons work unless I set dom.indexedDB.enabled to true. When will this be fixed?
I updated to Firefox 35 and then none of my add-ons worked. After 2 mins of googleing it is clear 1000's of others also have this problem: https://adblockplus.org/forum/viewtopic.php?f=1&t=27375&sid=96e0026dbd6abb532da3e52c81492f0b
The solution is to set dom.indexedDB.enabled to true. This seems like firefox 35 is broken. When is a fix coming? Its already been a few days.
All Replies (7)
cor-el said
See also:
Yeah, I read this one as well. So why is Mozilla not fixing it yet? 35 should have been pulled immediately. I can not believe the rape my eyes had to take when adblock was not working for a few days.
You will have to accept that disabling IndexedDB can break extensions and possibly websites as well. Firefox allows to make a lot of changes to setting and there can always be issues if you make such a change without understanding that things can get broken. You do get a warning screen when entering the about:config page for the first time. If you disable specific features that are used by extensions then it is up to you to decide what is more important: use the extension and enable the feature or disable the feature and can't use the extension. It is the same as blocking cookies via a specific block exception. Cookie exceptions also work for local storage.
Firefox 34 and later have a storage inspector that allows to see a website stores in local storage and cookies. It is part of the developer tools and can be enabled via the Toolbox Options (gear) icon in the Web Console (Firefox/Tools > Web Developer).
Fix what?
That pref is set to True by default in Firefox as installed. Someone or "something" changed that pref to that "userset" value of False.
further comments deleted after reading the Bug report that Philipp came up with
Modified by the-edmeister
I don't know if I can really believe that. 34 worked fine with all my add ons. Then 35 broke all functionality with my add ons. Maybe something did change it to false, but the add ons worked with it set as false in 34. Mozilla would had to have did 'something' in 35 that caused false to brake add ons. That 'something' should be fixed asap, or pulled.
fiddling with the dom.indexedDB.enabled preference is not recommended. that said, a fix for the issue should make it into firefox 36 (bug 1079355).
As of Firefox 36.0.1 (Windows Desktop)...
Why is there no fix for returning our Add-Ons to us, and return the Add-On Bar like we painstakingly had it for a year or more?
Why in the WORLD did Mozilla even THINK of touching / changing the Add-Ons and how they display, and without warning users ?
Now, most all of my carefully done installed Add-On icons are GONE, I can't make them appear no matter what I do.
Most all of the Add-On icons do NOT appear in the Customize view, so how in the world are we to get them back ?
Because the Add-On icons can not be seen even with "showing" the Add-On Bar, and the Add-On bar now rests at the screen bottom, NOT tucked into the menu bar area as I had them for over a year.
There is some "The Add-On Bar Restored" add-on, but it does little to fix the damage Mozilla did to my carefully crafted Firefox installation.
THIS IS INSANITY.
Hours of wasted time so far as Add-Ons and a distinct Add-On Bar is paramount to proper operations.
How dare Mozilla destroy our Firefox installation like this ?
Put it BACK the WAY IT WAS.
Joe Rotello / Knoxville, TN / USA