Closed Bug 552249 Opened 15 years ago Closed 15 years ago

Silverlight isn't being detected in Firefox 3.6 on Windows

Categories

(Websites :: plugins.mozilla.org, defect)

x86
Windows 7
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Assigned: ozten)

References

()

Details

Attachments

(2 files)

On http://www-trunk.stage.mozilla.com/en-US/plugincheck/, the latest shipping version of Silverlight [1] isn't recognized: File: npctrl.dll Version: 3.0.50106.0 3.0.50106.0 I'm guessing we need to just a JSON entry for it? [1] http://silverlight.net/getstarted/
I think this works on Windows XP. There is already http://plugins.stage.mozilla.com/en-us/plugins/detail/microsoft-silverlight I think the issue is a different mime-type or another mis-match. Can you the Browser Info and the two table cells from Silverlight when you go to this page on Windows 7 http://ozten.com/random/perfidies/debug.html
Input: application/x-silverlight application/x-silverlight-2 Output: [{"aliases":{"literal":["Silverlight Plug-In","Silverlight Plug-In"]},"releases":{"latest":{"id":"8","pfs_id":"microsoft-silverlight","name":"Silverlight Plug-In","vendor":"Microsoft","url":"http://www.microsoft.com/silverlight/get-started/install/default.aspx","modified":"2010-03-15T06:30:02+00:00","created":"2010-03-11T02:45:08+00:00","plugin_id":"30","os_id":"3","platform_id":"8","status":"latest","filename":"npctrl.dll","version":"3.0.40818.0","detected_version":"3.0.40818.0","detection_type":"original","manual_installation_url":"http://silverlight.dlservice.microsoft.com/download/C/5/B/C5BB5CD8-E871-49AC-8A40-61010E1FD1CF/Silverlight.exe","os_name":"win","app_id":"*","app_release":"*","app_version":"*","locale":"*","fetched":"2010-03-14T16:39:32-07:00","relevance":3},"others":[]}}]
(In reply to comment #3) Odd that this plugin returns the same literal twice. No regex, so I added one. Waiting for cache to clear. I couldn't repro at a Microsoft demo booth Sunday where they had Windows 7 and Silverlight... I'm setting up a Windows 7 VM locally, but it will take me several hours.
I think when I was setting up a regex it was failing. Filed IT Bug#553375
Summary: Silverlight isn't being detected → Silverlight isn't being detected in Firefox 3.6 on Windows
Okay, so the root cause was there was no releases with detection_type='version_available'. I'm thinking this will bite us again in the future. How to see if this is the issue next time: Go to the tester page for the plugin http://ozten.com/random/perfidies/tester.html#plugins=11.5.6.606&mimes=application/x-director Switch Second drop down from 'Original' to 'Version Available'. If the response is empty, we forgot to add a detection_type='version_available' release. I also found Shockwave missing this for Firefox on Windows 7. Fix it too with an additional release in plugins.stage.mozilla.com.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
FWIW, if this helps: If the version is the same between original and version_available styles, you can stick a "*" in for the detection_type and everything will match. If left empty, it defaults to original
I'm confused; application/x-director is for Shockwave, not Silverlight. Silverlight still doesn't have its version recognized on www-trunk.stage.mozilla.com/plugincheck, in Firefox 3.6
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #8) Sorry for the confusion, replace x-director with any mime type that is broken. Plugin isn't working right 1) Go to debug.html and scroll down to it 2) Click Test 3) If your on Firefox 3.6, try switching "Original" to "Version Available" This is a way to identify that the issue is detection_type version_available.
(In reply to comment #8) The data in plugins.stage.mozilla.com has changed since I've marked this fixed. I'll investigate.
So this was either user error or I don't know what is going on. Maybe I didn't push this live. I thought I did, but maybe I was testing with a Firefox3.6 that I had updated the plugins with (?). I don't think so, but that would allow me to get sandbox data instead of live data (?). I'm blocked by Bug#553615 to push this live.
Depends on: 553615
I have updated this. Please retest. We should add a simple audit trail soon, so we can better figure out these kinds of issues.
Still doesn't work; when I load http://ozten.com/random/perfidies/tester.html#plugins=3.0.50106.0&mimes=application/x-silverlight%20application/x-silverlight-2 and change the selector to "Version available," I get "[]" in the output section for the two MIME types: application/x-silverlight application/x-silverlight-2
(In reply to comment #13) This no longer works for me either. I'll try to repro this behavior. I'll probably have stage caching turned off. Twice I've updated the data and then it's been reverted later. Possibilities: 1) Another person editing the plugin 1.1) via admin/admin or another role? 2) Data never made it to the database and I "fixed it" in the cache only. After 1 hour the cache expires and we get the "bug" data.
Having a tough time reproducing this issue in dev. one difference is that I always have a sandboxed version of Silverlight in stage. Deleting that sandbox. Updated live plugin. Will check again in 1 hour to see results.
That didn't work.
6:45pm altered Silverlight - added regex and changed detection_type to '*' for both releases 6:50 (good) Refreshed edit screen and see same data 7:00 (bad) Refreshed edit screen and data had reverted Caching for database access is 1 hour.
Bug#553615 is blocking repro, but gives us a good way to test behavior with a possible logging error. 1) Edit a plugin's Literal from 'Totem' to 'TOTEM' 2) Save which POSTS 2 requests to plugins/detail/gnome-totem.json 3) Note after requests literal still says 'TOTEM' Actual: Refresh page, literal reverts to Totem so nothing was saved. User has no way of knowing their update failed. Expected: UI would display error. TOTEM would revert to Totem. I'll setup my dev env to reproduce. I'm wondering if this is an issue with shadow db setup?
Thanks to @lorchard for figuring this one out... A development feature that imports json files from plugins-info is probably causing a couple of staging issues: * Every day a new log file is created, owned by root instead of apache * Data in the database is reverted for some plugins but not others We are disabling the cron that runs 'util/import plugins-info/*.json'. 10:30 I've updated Silverlight metadata. We'll see in an hour if it gets reverted.
This appears to be fixed.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: