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

Jump to navigation Jump to search
Line 72: Line 72:
* [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=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 including FF 16 will see an infobar as an out of date (but not blocked) plugin
* 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 - Test Cases [http://bit.ly/IttYo3 here]
* Anything after FF 16 will have CTP blocklist enabled, out-of-date/vulnerable plugins will be blocked, in about:addons should be some indication of their vulnerable status
* Anything after FF 16 will have CTP blocklist enabled, out-of-date/vulnerable plugins will be blocked, in about:addons should be some indication of their vulnerable status


Confirmed users
891

edits

Navigation menu