Confirm
313
edits
Changes
no edit summary
Users can turn on preferences to require click to play for specific plugins.
Mozilla can remotely configure the users browser to require click to play for specific plugins that are out-of-date and/or vulnerable.
(Note that we may allow vendors a few days or a week to update their users before remotely requiring click to play on a plugin. This will depend on the severity of the vulnerabilities in the plugin.). The plugin blocklist may also be used in some cases, as it recently was to block widespread exploitation of Java.
|Feature ux design=When "click to play" plugins are found on a page, their start up will be delayed until a user performs interaction with the browser to enable the running of the plugin.
Implementation work starting in {{bug|711552}} 'Create click to play UI for desktop'
See also {{bug|737508711618}} 'Add the ability to remember plugin-activation settings'and {{bug|730318}} 'Opt-in activated plugins should use internal APIs to keep track of plugin activation' and {{bug|711618}} 'implement click to play permission model' .
{{bug|742753}} concerns only playing the instance of the plugin that has actually been clicked and also about some of the problems involved with 'invisible'/helper content - this has some prior history as well due to problems encountered when implementing click to play in Fennec.
