Add option to create a window with all add-ons disabled
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
People
(Reporter: sheppy, Unassigned)
Details
It would be incredibly cool and often handy to be able to create a window in which all add-ons are disabled, similar to how you can create a window with private browsing enabled. This would allow quick activities to be performed with sites that don't work right with your add-ons, or for comparison testing between what something does with and without add-ons, which would be useful for both add-on writers and testers, as well as for IT people.
For instance, right now I'm in a situation where a site isn't working. Support for the site tells me that it definitely works in Firefox. This means my next step is to see if it's an add-on thing. But that means wrapping up any in-flight activities, quitting the browser, and restarting it with add-ons disabled -- then restarting again afterward to get them back. Big waste of time, especially if you have lots of tabs and windows open. I could save tons of time just opening a new add-on-free window and trying it again there.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Add-ons Manager' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
Does the existing profiles feature work for you? Visit about:profiles, create a new profile if needed and then you can start a fresh instance of Firefox with default settings.
We have floated the idea of offering the ability to restrict add-ons to certain containers, but it's not close to ready yet (bug 1683056).
|
||
Comment 3•4 years ago
|
||
We're unlikely to do this exact thing you're asking for because it would involve UX for yet another mode, ways for users to control it, and APIs for extensions to find out if they should have access to specific window -- this is something that extensions need to know could happen and plan/account for.
But we're currently working on better UI and controls for restricting extensions access to certain pages in bug 1711787 (and blockers), as well as possible use of containers (as Rob mentioned) that together might cover most of the use cases you describe, so closing this as wontfix.
Description
•