Opt-in activation for plugins: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 64: Line 64:
#* '''Clicking to play one instance of the plugin will enable that instance and all hidden instances of the same plugin.  Other visible instances of the plugin will not be enabled until explicitly clicked. Plugins of other types are not  
#* '''Clicking to play one instance of the plugin will enable that instance and all hidden instances of the same plugin.  Other visible instances of the plugin will not be enabled until explicitly clicked. Plugins of other types are not  
activated'''
activated'''
Possible future use cases (ideas that need research):  
Possible future use cases (ideas that need research):  
# User has a plugin that is up-to-date and used within the last 30 days:
# User has a plugin that is up-to-date and used within the last 30 days:
Line 95: Line 96:
|Feature functional spec=See Users and Use Cases
|Feature functional spec=See Users and Use Cases


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).  
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.
|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.
|Feature implementation plan=Phase 1:
|Feature implementation plan=Phase 1:
Confirmed users
197

edits

Navigation menu