Opt-in activation for plugins: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
No edit summary
mNo edit summary
Line 3: Line 3:
|Feature stage=Development
|Feature stage=Development
|Feature status=In progress
|Feature status=In progress
|Feature version=Firefox 15
|Feature health=OK
|Feature health=OK
|Feature status note=Implementation started
|Feature status note=Implementation landed for 14, further work in 15.
}}
}}
{{FeatureTeam
{{FeatureTeam
Line 110: Line 111:
(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.
(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 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 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 ?
|Feature implementation notes=Meta bug for the work is {{bug|738698}}
|Feature implementation notes=Meta bug for the work is {{bug|738698}}


Confirmed users, Bureaucrats and Sysops emeriti
2,974

edits

Navigation menu