There are some Firefox extensions that require access to local storage and/or indexedDB, for example, to save data on the user device Firefox runs on. All these extensions may break if cookies are blocked. In this article, we’ll tell you about how to deal with Firefox extensions that require cookies. Read on.
Deal with Firefox Extensions That Require Cookies
Many extensions like uMatrix, uBlock Origin, or Stylus use the storage and thus require cookie permissions even if they do not set cookies to function properly. While some occur with fallbacks built-in to overcome this limitation, it’s best to address this head on instead as indexedDB usage is normally the better option to whichever fallback solution is employed.
One of the simplest ways to get to the profile folder is to load about:support, and then click on the Show Folder button on the page that appears. You need to check the storage/default directory of Mozilla Firefox profile if extensions use indexedDB. If you have folders starting with moz-extension, you have extensions that use it and thus require cookie access. Please note that the extensions are listed with their internal UUID and not their name. Also remember that the UUID is randomly assigned during the installation process. It means if you uninstall and reinstall or simply make use of the extension on multiple systems, it is different.
Firefox users have two options to address the issue. They are:
- Enable first-party cookies and regularly clean up cookies, or block cookies and storage
- Keep the deny all setting but use exceptions to allow extensions that require cookie access to use indexedDB storage to function properly
Set Cookie Exceptions for Extensions in Firefox
- To get started, you need to load about:debugging in Firefox
- The page lists all system add-ons along with all installed extensions of the Firefox browser
- Next, locate the browser extension that you would like to add exceptions for. You’ll find the internal UUID listed next to extensions that you have installed within the browser. This helps with the identification
- Now, you can click on Manifest URL underneath the extension listing
- You need to right-click on the page that opens and then select View Page Info from the context menu
- Once done, you can switch to the Permissions tab of the Page Info window
- Now, locate Set Cookies in the list of permissions. And you need to remove the checkmark from “use default”, and set it to allow
- You can repeat the process for any other extension that requires access to cookies
- Restart Firefox
Note: You can manage cookie permissions by navigating to Options > Privacy & Security > History > use custom settings for history > Accept cookies from websites, Exceptions. In addition, you may use the prompt to add cookie exceptions as well. All you need to do is simply copy the complete folder name, replace the +++ with ://, add it under “address of website” and set it to allow.
For example, moz-extension+++23bf26fb-1c8d-40d3-b7c2-798882a0d55c to moz-extension://23bf26fb-1c8d-40d3-b7c2-798882a0d55c.
CCleaner identifies extensions cookies but it makes no difference whether it wipes them or not as they get recreated automatically on the following start of the web browser.
So this was all about how to deal with Firefox extensions that require cookies.
You May Also Like: How to Fix YouTube Background Playback Feature on Firefox for Android