Confirm
313
edits
Changes
no edit summary
|Feature product manager=Asa Dotzler
|Feature feature manager=Justin Dolske
|Feature lead engineer=Blair McBrideJared Wein
|Feature security lead=David Chan (dchan)
|Feature privacy lead=Sid Stamm (geekboy)
|Feature requirements=* Ability to set autoplay, click-to-play or never play on any plugin
* Built-in whitelist for the most common plugins
|Feature ux design=* Settings: Render When 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. 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. Phase 1 of this project will be an "all or nothing" strategy. Adding another hurdle for drive-by attacks will be an improvement over where we are now. Future phases may incorporate a way for users to selectively enable specific plugin: types (AlwaysFlash vs. Java vs. Silverlight etc.). This implementation hasn't been designed or agreed upon yet, but it may be similar to the blocked-popup context menu.
|Feature implementation notes=Implementation work starting in {{bug|549697}}.
}}
|Feature secondary roadmap=User Experience
|Feature list=Desktop
|Feature project=Responsiveness
|Feature engineering team=Desktop front-end
}}
