Changes

Jump to: navigation, search

Opt-in activation for plugins

72 bytes added, 19:49, 25 April 2012
no edit summary
(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.). The plugin blocklist may also be used in some cases, as it recently was to block widespread exploitation of Java. When Phase 3 lands, User & Use Cases 1-7 will all have been implemented.
Phase 4: Explore Future Research User and possible future Use Cases 81-103. 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}}
Confirm
197
edits

Navigation menu