Created attachment 407052 [details] warning and link shown correctly (Namoroka on WinXP) 1) New profile in latest Shiretoko or stable Firefox 3.5, with the Flash plugin installed. 2) In about:config, set extensions.blocklist.url to https://bug455906.bugzilla.mozilla.org/attachment.cgi?id=346066 3) Force a blocklist update. Can be done by executing the following in the Error Console's code line: Components.classes['@mozilla.org/extensions/blocklist;1'].getService(Components.interfaces.nsITimerCallback).notify(null) 4) The blocklist window should now come up to tell you that Shockwave Flash is soft blocked, with the appropriate option to override. (the test list has other items not relevant to this test here) Allow it to be disabled and click the restart button. 5) When it comes back, go to the Add-ons Manager plugin pane. Note the Flash entry is now disabled, however it is shown the same as any other disabled plugin. 6) Exit and load up the same profile in latest Namoroka or Minefield. Check the entry in the Add-ons Manager again. This time it has the expected "Known to cause security or stability issues." warning label and "More Information" link. (screenshot attached) If you instead opt to not disable in step 4, no change is observable in step 5, however the line will still show correctly in step 6. You can also try Namoroka first then switch to Shiretoko or use separate profiles; 1.9.1 branch doesn't seem to be able to show it in any case. This feature seems to work fine for soft blocked extensions, however. Tested on both Windows XP and Linux. Note that 3.6a1 doesn't show the expected line; latest nightly is required for it to work correctly.
I have a simple fix in progress for this, would like to block the next available 1.9.1 release on this.
Created attachment 407063 [details] [diff] [review] patch rev 1 This is a backport of a few hunks of the patch in bug 514327 which properly checks the softblock state of plugins. Trying to work out if it is possible to test this automatically.
dave, if it cant be automated, please flag in-litmus? so we can get a manual test added into litmus.
Comment on attachment 407063 [details] [diff] [review] patch rev 1 Please request approval220.127.116.11? after you get reviews.
Comment on attachment 407063 [details] [diff] [review] patch rev 1 Looks good. Could you also update trunk with const nsIBlocklistService = Components.interfaces.nsIBlocklistService; and replace Components.interfaces.nsIBlocklistService with BlocklistService?
I don't think we can automate the testing here, we'll need a litmus test. The steps in comment 0 can provide a base.
(In reply to comment #5) > (From update of attachment 407063 [details] [diff] [review]) > Looks good. Could you also update trunk with > const nsIBlocklistService = Components.interfaces.nsIBlocklistService; > > and replace Components.interfaces.nsIBlocklistService with BlocklistService? Trunk already has this
It might be nice to cover both the plugin and extension case of this in the litmus test, if possible.
Comment on attachment 407063 [details] [diff] [review] patch rev 1 Approved for 18.104.22.168, a=dveditz for release-drivers
Looks like I accidentally had this patch already applied in my 1.9.1 tree when I landed bug 372980 so this has actually already landed in http://hg.mozilla.org/releases/mozilla-1.9.1/rev/2f9a687a93f1. I'll try to avoid this in the future.
Verified fixed with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:22.214.171.124pre) Gecko/20101105 Shiretoko/3.5.16pre That would be a perfect test for Mozmill.
The 1.9.1 branch will be abandoned soon so I will not add a Litmus test for it. In general the following test should be enough because we have a couple of automated tests meanwhile: https://litmus.mozilla.org/show_test.cgi?id=15309