Confirm
298
edits
Changes
no edit summary
Phase 2:
Mozilla can remotely configure the user's 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. When Phase 3 lands, User & Use Cases 1-7 will all have been implemented.
Phase 43: Explore possible future Use Cases 1-3. This needs more research. Can we leverage user behavior to define a heuristic of when a plugin should be click to play? Can we collect Telemetry data to help us understand how often plugins are used ?
|Feature implementation notes=Meta bug for the work is {{bug|738698}}
See also {{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.
Phase 1 landed in Firefox 14.
