Confirm
298
edits
Changes
no edit summary
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.
Also see {{bug|754472}}.
|Feature implementation plan=Phase 1:
Users can turn on a preference to require click to play for all plugins globally
(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 1Fix the bugs that prevent click-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 from being awesome (see {{bug|738698774937}}). These bugs are, for example, click-to-play breaking Youtube on OS X.
Phase 1 2 landed in Firefox 1416.
Phase 2 3 is under development currentlyway.
}}
{{FeatureInfo
