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.
We keep hearing about how this extremely obvious, necessary and seemingly extremely easy to implement idea for a feature has garnered attention, yet here we are at 0% progress.
Honestly, what is Firefox even developing if not specifically this?? I can't think of a single thing that could me more important than fixing this glaring security issue which would also double as a massive sortof QoL feature...
Firefox is still the best browser, but this is irritating; just do the thing already...
I’m surprised this feature is still missing. Firefox usually leads the way in privacy and customization. There should be an allow list and a block list, letting users specify domains or URLs.
That said, it’s probably not as simple as it sounds. Properly implementing this while preventing extensions from misusing cross-page access could be tricky. Some possible challenges include:
- Preventing Cross-Site Data Leakage (e.g., iframe access between allowed and blocked pages) - Handling Redirects and Dynamic URLs - Ensuring Extensions Can't Bypass Restrictions (e.g., injecting scripts indirectly)
Still, I hope Mozilla prioritizes this, as it would be a major improvement for user control and security!
Not even too sure how the file works from my OS, I tried managing the extensions manually, no luck at all, I've been on Firefox for 3 days, so I am not even too sure how extensions work
I've noticed that the iCloud Passwords extension is significantly slowing down Firefox, but only on one specific website (Reddit). It would be great if there were an option to disable specific extensions on a per-site basis, as the performance issue only occurs on that site. I do not want to disable the extension entirely so this would be actually a nice implementation.
Ability to toggle an addon's ability to read and modify sites, regardless of what it wants to have access to.
By default this change will be per session/visit (Allow Once), then will revert to default behavior, but can easily be made permanent (Allow according to Addon Permissions).
Also, give users the ability to choose what the default state of each addon is;
always able to read data (if Addon permissions require it) until temporarily changed,
or never read data for any site, (regardless of addon permissions), until temporarily changed.
This would be a middle ground between letting addons be active anywhere, having them disabled in the about:addons page, and having them uninstalled.
Call it temporarily disabling addons, or disabling them only for specific sites, or specifically choosing to have them only active on certain sites, and disabled everywhere else.
Ability to group addons, and restrict their ability to read and modify sites collectively, by using a toggle associated with the group, not individual addons.
Have these groups able to be associated with addons pinned to the toolbars as well as addons in the the Extensions Button menu.
(Groups I'd create include 'Adblockers' 'Quick Tools' 'Containers' 'Website Specific Enhancers'). That sort of thing.
This would allow something functionally like temporarily disabling all adblockers for a site without having to go addon by addon disabling each one in whichever way those addons are designed for.
