Firefox 115: some add-ons may be blocked from running on certain sites 😮

1 Like

Simply hell the f no.

If by Mozilla non-monitored addons are the ones that get blocked, how could they tell that they are unsafe or insecure at the first place? Some may be, but how would Mozilla know?

More:

It seesm like not even all the by-Mozilla-monitored addons are allowed either.

Also, the question still remains what are those “specific websites” on which these by Mozilla non-monitored addons will be disabled?

Whatever it is, I don’t like it … at all!

:woozy_face:

I’m withholding judgement until I know what it is. (I always have a pitchfork & burning torch to hand anyway).

2 Likes

Perhaps they should step up and put in place a mechanism to get rid of the “bad apples” already there.

If I have chosen to install a non-monitored addon and the browser let me do so, then I want it to run it wherever I want, taking the responsibility myself.

Anything, beyond perhaps a warning that I am running a non-monitored addon, is intrusive in my opinion.

Though, I agree with @dalto on:

The problem with that screenshot is that under Mozilla’s ‘regulations’ all add-ons that are not ‘recommended’ have that same warning. Which is nearly all of them… Even add-ons that have been around longer than the recommended/verified programme, and that are still supported today.

In my opinion, they need to rethink the add-on store, if they want to use the new feature effectively in the same way they say it may work.

:100:

2 Likes

I’d rather see that some sites are blocked! :rofl:

1 Like

Just disabled it…

// IPv6
user_pref("network.dns.disableIPv6", true);
// Extension monitoring Mozilla
user_pref("extensions.quarantinedDomains.enabled", false);
1 Like

If the extension you want to use doesn’t work then okay disable it. Otherwise it doesn’t matter if the extensions your using work. Everyone may be using something different and some people have way too many extensions anyway and that’s another issue.

I don’t drink milk. :rofl:

I think this setting in about:config is meant to disable risky add-ons listed on the website mentioned below.

extensions.blocklist.detailsURL	https://blocked.cdn.mozilla.net/
1 Like

Exactly…

1 Like

I’m sorry, Firefox thinks otherwise!!!
honka_memes-128px-40

I wonder if this new “feature” is related somehow with Youtube testing ‘three strikes’ rule to block users with ad blockers.

The timing tells me something…

Firefox users who run add-ons that are not monitored by Mozilla may notice a new notification in Firefox when they visit certain sites. The notification informs them that “some extensions are not allowed” and were blocked from running on that site.

Mozilla writes on a support page: “As of Firefox version 115, we have introduced a new back-end feature to only allow some extensions monitored by Mozilla to run on specific websites for various reasons, including security concerns”.

Mozilla makes no mention of the scope of this and the support article is extremely vague. The change is called Quarantined Domains by Mozilla.

Firefox users may undo the change in the following way:

  • Load about:config in the Firefox address bar.
  • Click Accept the Risk and Continue, if the prompt appears.
  • Search for extensions.quarantinedDomains.enabled.
  • Set it to FALSE.
  • Restart Firefox.

Mozilla should consider publishing detailed information about the blocking in which it reveals all blocking rules.

:man_shrugging:

I can read the 1st time, there’s no need for repeating same stuff :laughing:

@dalto have shown how silent that “notification” is, can’t you see how this can be abused for something that Firefox decided for whatever reason doesn’t fit their criteria of nice addon?

AdBlockers come to mind first obviously, for some friendly corporations…Especially considering Mozilla is funded mostly by Goolag these days.

That’s a very alarming move and a very bad defaults waiting to be abused, it’s just a bad mechanism overall, if we exclude power users who are able to revert this config setting…At least until such config setting is there and it can easily disappear one day.

Mozilla makes no mention of the scope of this and the support article is extremely vague.

This is alarming as well…silence is not nice when it comes to questionable decisions.

1 Like

I fixed it for you :wink:

I think the whole alarming thing is overblown. Who say’s it’s a questionable decision? Just because some people don’t like it? :thinking:

Edit: It’s their software. They have a right to do with it what they feel is needed. It’s no different than EndeavourOS making changes to it’s ISO. Some may not like it and or the explanation. Distro’s do this all the time.

I’ll just be silent! :zipper_mouth_face:

:see_no_evil: :hear_no_evil: :speak_no_evil: