522952 - Add WPF blocklist information to relevant support articles

Status: VERIFIED WONTFIX

(support.mozilla.org :: Knowledge Base Articles, task)

Description

[Matthew Middleton (:zzxc)]

All versions of the Microsoft .NET Framework Assistant and Windows Presentation Foundation (Silverlight) plugin have been blocklisted by bug 522777, so we need to update relevant articles:

https://support.mozilla.com/en-US/kb/Using+the+Silverlight+plugin+with+Firefox
https://support.mozilla.com/en-US/kb/Popular+Plugins
https://support.mozilla.com/en-US/kb/Video+or+audio+does+not+play

We should also have a new article specifically for this issue, as users are being notified on restart that the add-ons have been blocked.

Since Microsoft doesn't include version numbers in the extension or plugin, blocking only old versions wasn't possible.  Thus, another security update from Microsoft to update the plugin name and extension UUID will be needed to correct this, according to bug 522851.

Comment 1

[Matthew Middleton (:zzxc)]

It appears that the Windows Presentation Foundation plugin is separate from Silverlight, so Silverlight sites should still work.  (Unless they are relying on the user-agent string change from the .NET Framework Assistant or on the WPF plugin)

Comment 2

[Dave Garrett]

Yes, I just tested this and Silverlight can be installed and will work fine regardless of the Microsoft .NET Framework Assistant or Windows Presentation
Foundation. They're not related.

See bug 522777 comment 67 for removal instructions for the blocked add-ons.

Comment 3

[Dave Garrett]

Any support info should probably say that removal is optional, however.

Comment 4

[[:Cww]]

I'll write the article specifically for this one (since I was going to anyway).  Matthew, can you make sure that any other page that needs editing gets edited?  For now, Bo updated http://support.mozilla.com/en-US/kb/Add-ons+blocklist and I'll try to have an article up by this afternoon.

Comment 5

[Dave Garrett]

It might be a good idea to put a big link to:
http://support.mozilla.com/en-US/kb/Add-ons+blocklist
on this page somewhere:
https://www.mozilla.com/en-US/blocklist/

This way users who click the "more information" link in the blocklist or Add-ons Manager windows will have an easy way to reach the support page with the information they're looking for.

Comment 6

[Chris Ilias [:cilias]]

(In reply to comment #0)
> We should also have a new article specifically for this issue, as users are
> being notified on restart that the add-ons have been blocked.

Let's file a separate article bug for that.

Comment 7

[Dave Garrett]

Filed bug 523204 for comment 5.

Articles were handled in other bugs. Anything left in this one?

Comment 8

[Bartłomiej Brzozowiec (BartZilla)]

(In reply to comment #5)
> It might be a good idea to put a big link to:
> http://support.mozilla.com/en-US/kb/Add-ons+blocklist
> on this page somewhere:
> https://www.mozilla.com/en-US/blocklist/
> 
> This way users who click the "more information" link in the blocklist or
> Add-ons Manager windows will have an easy way to reach the support page with
> the information they're looking for.

And what if some user is looking for info about disabling addon blocklist functionality altogether? That info is currently missing in this KB article...

Comment 9

[Dave Garrett]

(In reply to comment #8)
> And what if some user is looking for info about disabling addon blocklist
> functionality altogether? That info is currently missing in this KB article...

I don't think a support article is the best place for that. The average user should not be disabling their blocklist. The pref is in about:config by default and trivial to find by anyone with the knowledge level that should consider touching it. If it was designed to be turned off easily it'd have a switch in the GUI somewhere. (you clearly may disagree, but this is not a bug to debate that; file a new bug if you really want it to be easier to disable, but don't be surprised if it gets a wontfix)

Comment 10

[Chris Ilias [:cilias]]

Updating summary, now that .net is not blocklisted.

Comment 11

[Matthew Middleton (:zzxc)]

WPF is no longer being blocklisted either, so these articles don't need information about it.

->WONTFIX