Plugin Check gives wrong results for some Macs
On a Mac running OS X 10.6.8 (Snow Leopard) or Earlier, Plugin Check indicates both Java Applet Plug-In and QuickTime Plug-in are out of date.
Steps to Reproduce: Tools -> Add-ons -> Plugins -> Check to see if your plugins are up to date
Results show: Java Applet Plug-in Update Now QuickTime Plug-in 7.6.6 Update Now
Explanation: 1. Prior to OS X 10.7 (Mountain Lion) Apple provided Java. Apple has not provided an update. [java.com's update requires Mac OS X (10.7.3 version and above)] 2. There is no update to QuickTime Plug-in 7.6.6 for some Macs; it is most recent for OS X 10.6.3 through 10.6.8.
Can Plugin Check be fixed? Can Macs get better support? (Some unaddressed bugs go back to Firefox 3.5 and before!)
Bewurke troch peter.s.cahan op
Keazen oplossing
I see your vote in: Bug 565832 - Plugin Check Indicating QuickTime Plug-in 7.6.3 is "Outdated"
7.6.6. reported also
don't make a new bug, it is ok. (i vote also)
thank you
Alle antwurden (16)
So you have Mac 10.8, so you can download Java 7 update 25 or later from java.com. Same with Quicktime, you can update to 7.7.1. I'm not sure what the issue is? Just update your plugins.
I'm running OS X 10.6.8 (Snow Leopard), not 10.8 (Mountain Lion). These updates are not available for 10.6.8. Java 7 requires OS X (10.7.3 version and above). [See java.com] The QuickTime update link does not have any download link for anything before Mountain Lion. Searching reveals no update for Snow Leopard beyond 7.6.6. Using Apple's Software Update does not find any updates for these, either. The issue is that Plugin Check reports wrong results (update needed vs no update available) for Macs running Snow Leopard.
The last time I checked, the Plugin Check site only recognizes the latest release as the current release. If your OS is not eligible for that release for some reason, the Plugin Check site doesn't have that level of information.
Thanks. Is there any way Plugin Check can take OS into account? Often there are updates that are for Windows (for example) but the Apple compatible version isn't ready yet.
Also, different major OS releases sometimes have different releases for the same update, often separated by up to a month. (This is true for both Windows and OS X.)
Actually, the site does look at OS, but at a high level, e.g., Windows vs. Mac, and not down to the version number.
This does work -- when I send a request impersonating Mac, I get a different "latest" version of QuickTime:
Windows: "7.7.4"
Mac: "7.6.6.0"
But that doesn't solve your issue of Apple not making that update available for your version of MacOSX. Unfortunately, I don't think this will be easy to solve.
Do you want to take a minute to submit the suggestion using:
Help > Submit Feedback
In that case, there is a slightly different problem. I am running QuickTime 7.6.6, but it is being reported as vulnerable (needing update).
I will pass on the feedback as well.
It's possible my impersonation was not successful... someday I'll get a Mac.
No, I think your impersonation was successful, in that you got a different version number for Windows vs. Mac. I think the problem may be that Plugin Check is not using the Mac values for my Mac, or the relational operator is incorrect somehow. You saw current version QuickTime = 7.6.6 My Version of QuickTime = 7.6.6 Plugin Check is reporting vulnerable, needs update. Therefore Plugin Check has a bug. Simple syllogism.
Hello, 7.6.6 for mac it seems not blocked !!!!!
https://addons.mozilla.org/en-US/firefox/blocked/p408
https://wiki.mozilla.org/QA/Desktop_Firefox/Plugins/Blocklisting/Apple_Quicktime#Production
probably a bug in plugin test (as peter.s.cahan said above)
thank you
Bewurke troch ideato op
Hi ideato, it seems that not every "old" version is blocked, and not every block is a hard block triggers a warning or a click-to-play message. The blocklist mechanism seems to involve a different set of judgments and data files than the plugin checker site, but they might be connected in a way I don't see.
Hello jscher2000
I do not think you're wrong, you are correct.
thanks
Hello ideato,
Bug 886895 makes no mention of Plugin Check. Should it? or should a separate bug report be made for Plugin Check.
Hello peter.s.cahan, you are right, yes, it needs a new bug report. If the the guys who work on the bug understand some correlation, then will make the correlation.
thanks
Bewurke troch ideato op
So what has to be done to have the NEW bug report made?
Keazen oplossing
I see your vote in: Bug 565832 - Plugin Check Indicating QuickTime Plug-in 7.6.3 is "Outdated"
7.6.6. reported also
don't make a new bug, it is ok. (i vote also)
thank you
Hi Peter, anyone can file a bug, although you need to create a new login on Bugzilla (or use a webmail login through Persona).
Here's a sample plugincheck bug: Plugincheck reports Adobe Acrobat 10.1.7 as outdated although it is not.
It's not so important to figure out all the different categories on the Bugzilla system, and someone will recategorize bugs as needed. You can just focus on a detailed enough description that people will be able to understand and follow-up on the issue.
In the process of looking up sample bugs, I found an old page that describes how the lookup works for version information. Not sure this is still current, but it's the only thing I've seen that has this level of detail: https://wiki.mozilla.org/Plugins:PluginDirectory/HowPluginDetectionWorks