1,492 bytes added,
07:50, 16 May 2011 {| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Opt-in activation for plugins]]
| {{StatusHealthy|status=}}
| N/A
| Justin Dolske
<section end="status" />
|-
|}
== Summary ==
Unknown or slow plugins shouldn't be allowed to run without user interaction.
== Team ==
* '''Feature Manager''': Justin Dolske
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''': Alex Limi
* '''Accessibility''':
* '''Security''':
* '''Privacy''':
== Release Requirements ==
* Ability to set autoplay, click-to-play or never play on any plugin
* Built-in whitelist for the most common plugins
== Designs ==
* Settings: Render this plugin: (Always|when clicked|never)
* When you have clicked a particular plugin on a given site 3 times or more, we should enable it automatically from then on if you haven't explicitly said otherwise.
* Optional, but interesting: Ability to soft-block 0-day using click-to-play.
== Next Steps & Open Issues ==
* Get estimates from Justin
== Related Bugs & Dependencies ==
== Risks ==
== Test Plans ==
== Goals ==
Make it harder for plugins to slow down Firefox.
== Non-Goals ==
== Other Stuff ==
Chrome already does something similar.
[[Category:Features]]
[[Category:Firefox]]
[[Category:Platform]]
__NOTOC__