Plugins/Firefox Whitelist

From MozillaWiki
Jump to: navigation, search

Plugin Whitelist Policy

NOTE: This policy has now expired. No new whitelist applications are being accepted, and existing whitelist entries will be removed in future Firefox releases.

Version 1.0

To improve the stability and performance of Firefox, and to safeguard the security of our users, Mozilla will block plugins by default, rather than automatically activating them. To ease this transition, and to support plugin and site authors making good faith efforts to move away from NPAPI-based plugins, we will implement a whitelist that exempts certain plugins from default blocking, if their authors satisfy specified requirements.

Though we believe that plugins are today both largely unnecessary and costly to the user experience, many of our users and developers still rely on a relatively small number of them for critical functions. We also recognize that authors need some time to adjust to web-based replacements. We therefore invite such plugin authors to apply for a short-term exemption to our plugin blocking policy.

This is the official Mozilla policy for whitelisting plugins. This policy consists of the following five sections:

1. Plugins blocked by default. Plugins will soon be blocked by default in Firefox. We will provide users with the choice of activating any and all plugins that we block as they come across pages that use them.

2. Applying for inclusion on the plugin whitelist. Plugin authors may apply for inclusion on a whitelist that will exempt their plugin from being blocked by default by filing a request in the Bugzilla system using this template. Each required field on the template must be completed before your application will be considered. Most importantly, the application must describe a credible plan the applicant is pursuing to migrate away from NPAPI-based plugins. Mozilla will evaluate the application and should it be accepted, the plugin will be whitelisted for 4 Firefox releases (for a total of 30 weeks 6 weeks in the Beta channel and 24 weeks on our general release channel). Inclusion in the whitelist will be at Mozilla’s sole discretion. Whitelist membership can be withdrawn at any time if we deem it to be in the best interest of our users.

3. Application window. The initial application window will be open until March 31st, 2014. Any application received prior to the end of this period will be reviewed and considered before plugins are blocked by default in Firefox. Applications received after this date will be processed as soon as a team of reviewers can get to them and, if accepted, added to the whitelist as soon as possible.

4. Re-application. At the close of the 30 week grace period granted to all first time applicants, plugin authors can re-apply for inclusion on the whitelist for another 24 weeks (successful re-applicants will not need to spend time on the Beta channel). Re-applications must be received 30 days prior to the close of the whitelisted period to guarantee continuous whitelisting.

5. Quality assurance. Plugin authors who are whitelisted are responsible for performing QA tests on our Beta Channel.

6. Blocking for Security and Stability Issues. Insecure plugins or plugins with serious stability issues will still be blocked according to the Mozilla addon blocklisting policy.

Please contact Mozilla at for more information about this policy and answers to related questions.

We reserve the right to change this policy in the future. We will do so only after consulting with the public Mozilla community, in order to ensure that all views are taken into account.

List of whitelisted Plugins

The list of accepted plugins for the whitelist can be found here