Opt-in activation for plugins/Test Plan: Difference between revisions

Jump to navigation Jump to search
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=760625 bug 760625] - use the blocklist to inform click-to-play plugins
* [https://bugzilla.mozilla.org/show_bug.cgi?id=754472 bug 754472] - click-to-play: implement multiple plugin doorhanger ui
* [https://bugzilla.mozilla.org/show_bug.cgi?id=793338 bug 793338] - click-to-play: implement multiple plugin doorhanger ui (vulnerability status bits)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=772897 bug 772897] - Implement UI for plugins made click-to-play by the blocklist
* [https://bugzilla.mozilla.org/show_bug.cgi?id=793273 bug 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
Confirmed users
891

edits

Navigation menu