#CLICK TO PLAY PLUGINS CHROME UPDATE#
outdated flash on YouTube) and for whatever reason cannot or will not update (outdated version of a plugin is required for their job, for example):
Use cases with proposed interactions below emphasized: Giving users better control over when and how plugins run would significantly reduce CPU utilization.Ĭhrome has implemented something similar: 2. Flash consuming 30% of the CPU because of many ads and movies). Java starting because a given page requested it), and in aggregate (i.e. Performance: Plugins consume significant resources, both individually (i.e.Providing a warning (or prompting for an update, if one is available) provides a defense against drive-by attacks, while allowing other plugins to run on popular sites. Security: Out of date plugins are the most common source of user compromise.This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.) Known vulnerable plugins shouldn't be allowed to run without user interaction.
To enable this feature, we need to figure out a UI notification mechanism that allows the user to understand persistently permitted/denied permissions.
Can content differentiate between "click to play" and "hard-disabled for security reasons"?.
#CLICK TO PLAY PLUGINS CHROME INSTALL#
Pandora) so that they can show alternate UI (plugins are disabled, please click to play) instead of timing out and showing a generic "please install Flash" or "Song initialization timed out, please hit refresh" UI." Bsmedberg asks in bug 711552: "Are we exposing to the DOM that a particular plugin element ( or is user-disabled?) This seems important for websites that rely primarily on plugins (e.g.Adverse reactions between content plugin sniffing and click-to-play.Initial minimal implementation landed for 14 (opt-in), further work in 15 and 16. Please use "Edit with form" above to edit this page.