Confirm
717
edits
Changes
no edit summary
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 1516
|Feature health=OK
|Feature status note=Implementation Initial minimal implementation landed for 14(opt-in), further work in 15and 16.
}}
{{FeatureTeam
* An "allows block plugins on this site" options could leave a site broken and confuse the user. To enable this feature, we need to figure out a UI notification mechanism that allows the user to understand persistently permitted/denied permissions.
|Feature overview=Out of date (and hence, likely Known vulnerable) plugins shouldn't be allowed to run without user interaction.
This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)
# Security: Out of date plugins are the most common source of user compromise. Providing a warning (or prompting for an update, if one is available) provides a defense against drive-by attacks, while allowing other plugins to run on popular sites.
A long-term future goal is also:
# Performance: Plugins consume significant resources, both individually (i.e. Java starting because a given page requested it), and in aggregate (i.e. Flash consuming 30% of the CPU because of many ads and movies). Giving users better control over when and how plugins run would significantly reduce CPU utilization.
