Confirmed users
717
edits
Opt-in activation for plugins: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
|Feature stage=Development | |Feature stage=Development | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Firefox | |Feature version=Firefox 16 | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note= | |Feature status note=Initial minimal implementation landed for 14 (opt-in), further work in 15 and 16. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 39: | Line 39: | ||
* 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. | * 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= | |Feature overview=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.) | This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.) | ||
| Line 46: | Line 46: | ||
# 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. | # 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 | A 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. | # 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. | ||