Confirmed users
304
edits
No edit summary |
No edit summary |
||
Line 107: | Line 107: | ||
Phase 2: | 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. | 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.) | (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.). | ||
Phase | Phase 3: 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}} | |Feature implementation notes=Meta bug for the work is {{bug|738698}} | ||
See also {{bug|711618}} 'implement click to play permission model' | See also {{bug|711618}} 'implement click to play permission model' | ||
Line 123: | Line 117: | ||
{{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. | {{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. | Phase 1 landed in Firefox 14. |