canmove, Confirmed users
285
edits
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 24: | Line 24: | ||
* Where are the preferences to require click to play for all or specific plugins? Where are the preferences to have separate plugin permissions per-site? | * Where are the preferences to require click to play for all or specific plugins? Where are the preferences to have separate plugin permissions per-site? | ||
* What | * What warnings show up when a user wants to enable an out of date plugin? What does the UX of the "scary warning" look like? Do we direct them to the plugin check website? Do we have two levels of warnings (scary and really scary) and what would they look like? | ||
* Adverse reactions between content plugin sniffing and click-to-play | * Adverse reactions between content plugin sniffing and click-to-play | ||
| Line 86: | Line 86: | ||
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. | 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 notes=Meta bug for the work is {{bug|738698}} | |Feature implementation notes=Meta bug for the work is {{bug|738698}} | ||