User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 Build ID: 20150807094550 Actual results: Currently it is possible to blacklist single gmp-plugins for example with media.gmp-gmpopenh264.enabled or to blacklist all gmp-plugins with media.gmp-provider.enabled. Expected results: Maybe there could also be a whitelist to enable single gmp-plugins which would then prevent gmp-plugins from new Firefox versions to be enabled automatically.
There is no need for this. We only use a GMP plugin if we have specific code in the platform that looks for it, so we only load the we already know about (clearkey, OpenH264, and Adobe Primetime) and any others would do nothing.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
I have troubles to fully understand your post. At least here is a use case I have thought of: The user wants to have a specific gmp-plugin (for example Adobe Primetime to look videos on Netflix) but doesn't want that any future version of Firefox does automatically download and enable another new gmp-plugin.
That kind of custom config is not something we will support. The complexity cost of the additional prefs (hidden or visible) is too high.
You need to log in before you can comment on or make changes to this bug.