Closed Bug 431335 Opened 17 years ago Closed 17 years ago

Blocklist Silverlight 2 beta 1 Plugin

Categories

(Toolkit :: Blocklist Policy Requests, defect)

Product:
Toolkit
Component:
Blocklist Policy Requests
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: polidobj, Unassigned)

Details

The silverlight plugin is causing an increasing amount of crashing (see bug 421217). It's topcrash #3 in 3.0pre and #4 in 3.0b5. Blocking version 1 is the least to do. Blocking version 2 beta 1 which crashes too could be harder because the version in about:plugins is 1.0.30226.2. Although that could mean it would be blocked with version 1. I hear that Microsoft expects to have this fixed in version 2 (probably by beta 2). I have heard nothing about an update to version 1 to fix this problem.
Bah I got mixed up thinking that affected version 1. And I guess it's not worth blocking a beta version of a plugin.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
i disagree. there's nothing wrong with blocking a beta that you know doesn't work. as for "hearing", well um... atm it's mostly our fault....
I suppose it could be worth it because there are almost 7000 crashes reported for beta 5 and that's despite Bug 422308 which could be preventing who knows how many more crashes from being reported. Aside from that, the crash bug has pretty much died since they minused the bug from blocking.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: Blocklist Silverlight Plugin. → Blocklist Silverlight 2 beta 1 Plugin
I don't think blocklisting a beta (which is supposed to have issues with it and is opt-in) is a good use of the blocklist service.
Is it even feasible with the versions like this: version 1 of the plugin has this version in about:plugins: 1.0.30401.0 Version 2 beta 1 is actually a lower version number: 1.0.30226.2 Version 2 beta 1 does have an extra MIME type listed: application/x-silverlight-2-b1
All we have is name, description and filename -- a combination of regexps could be used to trigger off those, but if the plugin doesn't have version info in any of those, we're SOL.
Won't block because it's a development version. See comment #4.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → WONTFIX
Verified WONTFIX
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → Toolkit
You need to log in before you can comment on or make changes to this bug.