Confirm
197
edits
Changes
no edit summary
|Feature open issues and risks=* What type of UX to have for allowing users to opt in (or out) of enabling plugins on a (semi)persistent basis? See below in "Use Cases".
* How do we manage these click to play settings? Deliver via our existing blocklist mechanism? New system?
* 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 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 users to the plugin check websiteas part of the warning? 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
Chrome has implemented something similar: http://blog.chromium.org/2011/03/mini-newsletter-from-your-google-chrome.html
|Feature users and use cases=Use cases with '''proposed interactions below emphasized''':
# User has a plugin where that mozilla has remotely required to be click to play because the plugin is vulnerable, but no update available
#* User cannot run plugin or
#* '''User can run plugin after scary warning'''
# User has a plugin where that mozilla has remotely required to be click to play because the plugin is vulnerable, and an update is available
#* '''User is prompted to open plugin-check/update page, but can run plugin after scary warning instead'''
# User is tired of always clicking to play a given plugin (i.e. outdated flash on YouTube)
#* '''User can right click on the overly overlay and check an option to always allow this specific out-of-date version on the specific domain.'''
#* Jruderman has suggested a context menu instead of a click - this is a mitigation against click jacking. Could provide "Now/Always/Never" choices.
# User has a plugin that requires click to play, but it is not visible on the page.
Phase 3:
Users can turn on preferences to require click to play for specific plugins.
Mozilla can remotely configure the users browser to require click to play for specific plugins that are out-of-date and/or vulnerable.<br/>(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.
|Feature ux design=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.
