4 ms·
That doesn't make sense. If the true purpose of this was to give organizations (or individual users) the ability to control specific websites that extensions c
by Someone1234 3y ago
That doesn't make sense.
If the true purpose of this was to give organizations (or individual users) the ability to control specific websites that extensions couldn't run on for security/sensitivity reasons, then why is it only a subset of extensions that Mozilla determines?
A true user-defined restrict list could, in theory, be a useful feature but as I said, this feature is NOT "here's a list of websites, don't allow ANY extensions to run on it" it is instead "Mozilla is supplying a list of websites, which you can override, but in both cases Mozilla will determine which 'trusted' addons can run on those specific websites using rules/procedures only Mozilla knows and controls."
Claiming this is meant to be org/user controllable is very inaccurate. Just because there's some about:config stuff doesn't mean a Mozilla website list and a Mozilla "trusted" addon list are anywhere close to "intended to be user defined." In fact the evidence shows that is objectively not true.
- DistractionRect 3y agoThere's some confusion here that needs to be dispelled. First, there's two categories of add-ons: - add-ons that get audited by Mozilla - add-ons that do not The ones they audit enjoy Mozillas endorsement in the app store, and an exemption from the quarantined sites setting. The quarantined sites setting only differentiates between the two categories. The audited apps are known to be non malicious, so they are exempt from the quarantined sites setting. The other add-ons are unknowns, and this sets a default access level. The ability to granularly opt extensions in/out is being worked on, and will likely ship with 116, per the comment I linked: https://bugzilla.mozilla.org/show_bug.cgi?id=1837670 https://bugzilla.mozilla.org/show_bug.cgi?id=1837670