Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How Do I Remove FF Restriction in about:config?

  • 11 replies
  • 1 has this problem
  • 10 views
  • Last reply by user1469512

more options

I'm usnig the latest ff 63.0.3 on win 10 1809. I'm trying to remove a restriction in ff in about:config by using 'privacy.resistFingerprinting.block_mozAddonManager' and clearing 'extensions.webextensions.restrictedDomains'. But sadly this doesnt work in lifting the restriction. Any ideas?

I'm usnig the latest ff 63.0.3 on win 10 1809. I'm trying to remove a restriction in ff in about:config by using 'privacy.resistFingerprinting.block_mozAddonManager' and clearing 'extensions.webextensions.restrictedDomains'. But sadly this doesnt work in lifting the restriction. Any ideas?

All Replies (11)

more options

So what error detail that is leading to cause this problem your having?

more options

Please reset these prefs via the right-click context menu to the default value. These prefs are there for a reason and you shouldn't be modifying them.

What issue(s) do you have that makes you remove a restriction?

more options

Similar thread: https://support.mozilla.org/questions/1242590

There's no way for extensions to inject content scripts into pages on addons.mozilla.org.

more options

WestEnd said

So what error detail that is leading to cause this problem your having?

No error comes up. Just that when i use an addon to theme pages (Dark Reader), pages like addons.mozilla.org remain unthemed. I tried this before I had reinstalled ff and it worked. For some reason now it doesnt work which is very strange.

more options

cor-el said

Please reset these prefs via the right-click context menu to the default value. What issue(s) do you have that makes you remove a restriction?

Why should I reset them??

As I mentioned before, when i use an addon to theme pages (Dark Reader), pages like addons.mozilla.org remain unthemed. I tried this before I had reinstalled ff and it worked. For some reason now it doesnt work which is very strange.

more options

jscher2000 said

Similar thread: https://support.mozilla.org/questions/1242590 There's no way for extensions to inject content scripts into pages on addons.mozilla.org.

No offense but youre wrong. Before I reinstalled FF I was able to theme addons.mozilla.org with the same version of FF.

Modified by user1469512

more options

koolx said

jscher2000 said
Similar thread: https://support.mozilla.org/questions/1242590 There's no way for extensions to inject content scripts into pages on addons.mozilla.org.

No offense but youre wrong. Before I reinstalled FF I was able to theme addons.mozilla.org with the same version of FF.

I guess I should test for myself before making pronouncements and not rely on other posters...

If I clear the restrictedDomains preference

and create a new boolean preference named

privacy.resistFingerprinting.block_mozAddonManager

and set it to true

and then reload an extension's page bypassing the cache,

the content scripts do get injected as you said in Firefox 63.0.3.

Now... to get back to normal.

more options

By the way, a safer way to dark theme privileged websites is ShadowFox. https://github.com/overdodactyl/ShadowFox

more options

jscher2000 said

By the way, a safer way to dark theme privileged websites is ShadowFox. https://github.com/overdodactyl/ShadowFox

I tried to install this but win defender warned of a possible risk.

And I cant find this addon in the addons.mozilla.org. Why is that do you think?

It doesnt install through ff since its an exe which is strange. Any thoughts?

Is it safe?

.

more options

ShadowFox installs through the optional userChrome.css and userContent.css files. It is a style rule override, not an extension. Please read through their documentation for more info.

more options

jscher2000 said

ShadowFox installs through the optional userChrome.css and userContent.css files. It is a style rule override, not an extension. Please read through their documentation for more info.

Appreciate it.