Confirmed users
891
edits
Paul.silaghi (talk | contribs) |
Paul.silaghi (talk | contribs) |
||
| Line 73: | Line 73: | ||
* [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 | ||
* 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 [http://bit.ly/IttYo3 Test Cases] | ||
* 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 | ||