There should be a way to allow extensions to execute only on specific websites like the Site access option in Edge does, this improves extensions usability and may also enhance privacy.
Important feature, please implement
I second this motion. Enabling an extension to run on all websites, when it is only utilized on one website, is undesirable; as it increases the surface vector for attack in vain.
Here's an example of a problematic extension. Grammarly. It can be rather invasive and annoying when doing most things, constantly calling back home to do what it needs to do. This isn't malicious, but rarely desirable outside of things like google docs or similar editors.While Grammarly has a way to disable it for certain websites, it's a blacklist. So you have to do it for every single website you don't want it to run on. It's in Grammarly's interest to force this on everything (probably to train their AI), but I certainly don't want that.This kind of feature would allow us to say "no, you only run on google docs and 365 word".
Love this! Please implement!
Any recent update on the status of this feature?
It's definitely one of the biggest QoL features that would be pretty useful for many users.
@BiMS (and others following along) let me check with the team to see if there are any recent updates to share
@Jon much appreciated
Hey @Jon, so, any news to report? It's been years by now. This is a thoroughly missed feature in Firefox.
Keeping a close eye on this thread. This feature is sorely needed to reign in some overzealous extensions, like Grammarly that's been mentioned before, among others.
This crucial security feature was proposed on March 2, 2022, but as of September 16, 2024, it remains unimplemented. This is quite concerning.
I’m troubled by the fact that add-ons installed for one particular website can function on other sites as well. For instance, I installed a currency converter add-on for one specific site, but it’s now interfering with and disrupting data in another site where it shouldn’t have any access.
Just wanted to say that this should work before installing an extension. AFAIK on chromium-based browsers you can limit extension to a particular website only after installing an extension. Which makes much less sense if you've already installed it with all permissions. Correct me if I'm wrong.
Jon Community Manager08-27-2024 05:38 PM @BiMS (and others following along) let me check with the team to see if there are any recent updates to share
So uh it's been two months - I'm guessing there aren't any updates?
This option seems pretty essential to security - especially if you're using something like violentmonkey to inject scripts.
Sorely missing the option to selectively enable / disable extensions according to domain name.
Back with an update:
Allowing extensions to run on certain websites is not currently in development, but it's in the backlog as a potential candidate for 2025.
This is so obvious. It would also reduce fingerprinting since sites that use it would generally only see a very common list of must-haves.