Opt-in activation for plugins: Difference between revisions

Jump to navigation Jump to search
no edit summary
mNo edit summary
No edit summary
Line 99: Line 99:
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 (as much as possible).
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 (as much as possible).
|Feature ux design=Visible plugins will have a chrome-privileged overlay that users will click on to activate the plugin. Invisible (or barely visible) plugins will cause an infobar to appear to enable all plugins on the page.
|Feature ux design=Visible plugins will have a chrome-privileged overlay that users will click on to activate the plugin. Invisible (or barely visible) plugins will cause an infobar to appear to enable all plugins on the page.
Also see {{bug|754472}}.
|Feature implementation plan=Phase 1:
|Feature implementation plan=Phase 1:
Users can turn on a preference to require click to play for all plugins globally
Users can turn on a preference to require click to play for all plugins globally
Line 106: Line 108:
(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 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?
Phase 3: Fix the bugs that prevent click-to-play from being awesome (see {{bug|774937}}). These bugs are, for example, click-to-play breaking Youtube on OS X.
|Feature implementation notes=Meta bug for the work is {{bug|738698}}


See also {{bug|711618}} 'implement click to play permission model'
Phase 4: 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?
and {{bug|730318}} 'Opt-in activated plugins should use internal APIs to keep track of plugin activation'.
|Feature implementation notes=Meta bug for the work is {{bug|738698}}. Please file any bug relating to click-to-play as blocking that bug.


{{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.
Phase 2 landed in Firefox 16.


Phase 2 is under development currently.
Phase 3 is under way.
}}
}}
{{FeatureInfo
{{FeatureInfo
Confirmed users
299

edits

Navigation menu