Confirmed users
891
edits
Opt-in activation for plugins/Test Plan: Difference between revisions
Jump to navigation
Jump to search
Opt-in activation for plugins/Test Plan (view source)
Revision as of 14:18, 28 September 2012
, 28 September 2012→Plugins to blocklist with Click-to-Play
Paul.silaghi (talk | contribs) |
Paul.silaghi (talk | contribs) |
||
| Line 66: | Line 66: | ||
* Mozilla can remotely configure the user's browser to require click to play for specific plugins that are out-of-date and/or vulnerable. | * Mozilla can remotely configure the user's browser to require click to play for specific plugins that are out-of-date and/or vulnerable. | ||
* [https://bsmedberg.etherpad.mozilla.org/ff15-ctp-blocklist-proposal Click-to-Play Blocklist Proposal] | * [https://bsmedberg.etherpad.mozilla.org/ff15-ctp-blocklist-proposal Click-to-Play Blocklist Proposal] | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=793273 793273] - FF16 CTP blocklist should never be triggered | * [https://bugzilla.mozilla.org/show_bug.cgi?id=793273 bug 793273] - FF16 CTP blocklist should never be triggered | ||
* Anything before FF 16 will see a CTP block as an out of date (but not blocked) plugin and use the old UI for that | * Anything before FF 16 will see a CTP block as an out of date (but not blocked) plugin and use the old UI for that | ||
* FF 16 will use what we currently have for ordinary click-to-play plugins, which says nothing about the security status of the plugins in question | * FF 16 will use what we currently have for ordinary click-to-play plugins, which says nothing about the security status of the plugins in question | ||