Confirm
197
edits
Changes
no edit summary
Chrome has implemented something similar: http://blog.chromium.org/2011/03/mini-newsletter-from-your-google-chrome.html
|Feature users and use cases=Use cases with '''proposed interactions below emphasized''':
# User has an out of date a plugin that is used on mozilla has remotely required to be click to play because the site the user plugin is visitingout of date (implying an update has been released) :
#* '''User can run plugin after clicking to activate it'''
# User has a plugin that mozilla has remotely required to be click to play because the plugin is being widely exploited, no update available
* Mitigate attacks where user interacts with site (clickjacking, or simply wants to run vulnerable plugin)
|Feature non-goals=We can't prevent users getting owned up by vulnerable plugins if they choose to activate a plugin on a site hosting malicious payloads. This is why driving plugin updates is important.
Warning the user of a newly installed plugin - this is part of another feature : https://wiki.mozilla.org/Features/Firefox/Improved_plugin_installation_and_management_experience
|Feature functional spec=Phase 1:
Users can turn on a preference to require click to play for all plugins globally
