Restricting plugins to profiles

NEW
Unassigned

Status

()

P5
enhancement
6 years ago
3 years ago

People

(Reporter: sworddragon2, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130218103006

Steps to reproduce:

I wanted to create a new profile for development reasons which should be restricted to specific addons/plugins.


Actual results:

Firefox reads plugins as last instance from the global profile-plugin directory so it is not possible to restrict plugins to a specific profile.


Expected results:

Firefox should read plugins from a plugin directory in the profile as last instance. This way for example I could put the flash debug plugin to my develop profile and the flash plugin to my default profile.
(Reporter)

Updated

6 years ago
Severity: normal → enhancement
Component: Untriaged → Startup and Profile System
OS: Linux → All
Product: Firefox → Toolkit
Hardware: x86_64 → All
Version: 19 Branch → Trunk
marking new as valid enhancement request
Status: UNCONFIRMED → NEW
Component: Startup and Profile System → Plug-ins
Ever confirmed: true
Product: Toolkit → Core
Priority: -- → P3

Comment 2

6 years ago
I'd take a patch (add a pref to disable global plugin loading). But I don't think it's something I'd ever prioritize.
Priority: P3 → P5
(Reporter)

Comment 3

3 years ago
I think the easiest would be if local plugins would be always have a higher priority than global plugins. For example profile-specific plugin -> global profile plugin -> plugins somewhere in system paths.
(Reporter)

Comment 4

3 years ago
Edit: Having additionally an option to disable global plugin loading as you suggested would be a nice enhancement too.
You need to log in before you can comment on or make changes to this bug.