Always expose version number of plugin

RESOLVED FIXED

Status

Websites
plugins.mozilla.org
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: espressive, Assigned: espressive)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
When displaying plugins on plugin-check, always display the version number of the plugin not only for up to date plugins.
(Assignee)

Comment 1

4 years ago
Initial version of this is on stage at the moment, but there are some tweaks remaining. At the moment, the biggest problem seems to be that no version numbers are set for IE.

Comment 2

4 years ago
Created attachment 8436396 [details]
IE10-Flash-13-0-0-206-Tested-on-2014-05-20.jpg

(In reply to Schalk Neethling [:espressive] from comment #1)
> Initial version of this is on stage at the moment ...

As I said in bug 1020133 comment # 1 I think this is an excellent enhancement.

> ... is on stage at the moment ...
FYI, I am now seeing it on LIVE as well as STAGE.
I did not expect this (but I'm happy).

So, using Fx 29.0.1 on
https://www.allizom.org/en-US/plugincheck/ STAGE
and
https://www.mozilla.org/en-GB/plugincheck/ LIVE (GB)
I get identical results.

For example I see, for "Adobe Acrobat", in the Status column
> Up to Date
> 11.0.7.79

Aurora (31.0a2) is, as you know, still having issues with Adobe Acrobat.
My POV is to give feedback, I'm not trying to 'force the pace of change'.


(from comment #1)
> At the moment, the biggest problem seems to be that no version numbers are set for IE.

I recall, from bug 861407 "new plugin checker not working on IE"
that IE 11 was not working (but older versions were).

  At the time I wondered if this might be related to 'security enhancements'
  (I'm being deliberately vague in this phrase) - in IE 11.

  I am thinking of, in IE 9,
  Tools, Internet options, "Security" Tab, 
  selected "Enable Protected Mode (requires restarting Internet Explorer)".

  I also think that the "Protected Mode" might be the default in IE 11.
  So, if you have someone to help you - who has IE 11 - this might be a clue.
  Having said that, I have now done some tests in IE 9 with "Protected Mode" on.


In bug 1010132 comment # 17 (posted on 2014-05-21) I was able to 'detect Flash (ActiveX)' on IE 10.

I have checked on IE 9 today.
  To start with I had an "Internet Explorer cannot display the webpage" message.
  After a few "Refresh" commands I was able to check on both STAGE and LIVE.
  In the past, IIRC, I have sometimes had to resort to http:// (not https://) for
  plugincheck on IE.  So the small delay in getting the plugincheck site
  to 'display' might be 'doing the certificate check' e.g. CRL or OCSP.
  Today I do get, on LIVE, https://www.mozilla.org/en-GB/plugincheck/  a
>      DigiCert has identified this site as:
> 
>      Mozilla Foundation
>      Mountain View, CA
>      US
I don't get this on STAGE (but would not expect to).
Remember, I hardly ever use IE.

Using IE 9 64bit - I get an 'expected result'.
Using IE 9 32bit - I get an 'expected result'.

All 4 results have:
"Shockwave Flash" is "Up to Date" BUT NO VERSION NUMBER is given in the "Status" column.
I think this is what you mean when you said:
> At the moment, the biggest problem seems to be that no version numbers are set for IE.

IIRC, this is how plugincheck has always been for IE.

However, you *do* get the 'Version Number' as 'line two of the Plugin Name'.
AND, you *do* get the 'Version Number' as 'line two of the Plugin Name'
EVEN WHEN the Plugin is "Vulnerable".

See "IE10-Flash-13-0-0-206-Tested-on-2014-05-20.jpg".
Here you see
> Shockwave Flash 13.0.0.206
as the 'line two of the Plugin Name'.
Correct and good.  Flash was out of date on 2014-05-20. I had not previously uploaded this JPG.

I had *reported* it as part of bug 1010132 comment # 17
> First, the good news:
> - IE 10 was able to detect Flash 13.0.0.206 (ActiveX) as "vulnerable" - correct.
> - IE 10 after updating Flash to 13.0.0.214 (ActiveX) reported "Up to Date" - correct.
> 
> Less good news (but I personally would use Microsoft's "Windows Update" to 'check this
> and Update as required'):
> 
> - IE 10 was able to detect Windows Media Player Plug-in Dynamic Link Library 12.0.7601.17514
> as "Up to Date" - I don't think this is correct.
> 
> - IE 10 after updating, Windows Media Player Plug-in Dynamic Link Library 12.0.7601.18150
> reported "Up to Date" - correct.

So, you can see this in "IE10-Flash-13-0-0-206-Tested-on-2014-05-20.jpg".

On my tests today, using IE 9, I get
> Shockwave Flash 13.0.0.214
as the 'line two of the Plugin Name'.
Correct and good.

The difference between the IE 10 on 2014-05-20 and the IE 9 on 2014-06-07
is that you now get the text "Up to Date" in the "Status" column.
Previously, in IE, you got 'white space' in the "Status" column if the 'plugin was OK'.
As seen in "IE10-Flash-13-0-0-206-Tested-on-2014-05-20.jpg".


On Fx (any version) you do NOT get the 'Version Number' as 'line two of the Plugin Name'.
You only get a 'partial version' e.g.
"Shockwave Flash 13.0 r0" for "13.0.0.214" or
"Adobe PDF Plug-In For Firefox and Netscape 11.0.07" for "11.0.7.79"

See an example I posted earlier in bug 1020133 comment # 1:
> Used Aurora on Stage:
> https://www.allizom.org/en-US/plugincheck/
> 
> See "Fx31-plugincheck-STAGE-2014-06-03.jpg".
> https://bug1010132.bugzilla.mozilla.org/attachment.cgi?id=8433727
> 
> Here, "Adobe Flash Player" 13.0.0.214 is Reported as "Up to Date" - correct - good.
> BUT, "Adobe Acrobat NPAPI Plug-in" is Reported as "vulnerable" - WRONG.

So, while I would be wonderful to have something like
> Up to Date
> 13.0.0.214
For the Shockwave Flash "Status" column, when using IE, the fact that you can see the
'Version Number' as 'line two of the Plugin Name' is useful.
As seen in "IE10-Flash-13-0-0-206-Tested-on-2014-05-20.jpg" you get this
even when the plugin is "vulnerable".

My questions include:

- How come you can't get the 'Version Number' as
    'line two of the Plugin Name' in Firefox?

- Is this 'the plugin author (e.g. Adobe) not putting the data in the file'?
    It could well be.  The ActiveX plugins are different files from the Fx plugins.

- Is this 'the plugin service using a different field from the plugin' in IE vs Fx?

- As you CAN get the 'Version Number' as 'line two of the Plugin Name' in IE
    can you use this data for the "Status" column?

DJ-Leith
(Assignee)

Comment 3

4 years ago
(In reply to DJ-Leith from comment #2)
> 
> My questions include:
> 
> - How come you can't get the 'Version Number' as
>     'line two of the Plugin Name' in Firefox?
> 
> - Is this 'the plugin author (e.g. Adobe) not putting the data in the file'?
>     It could well be.  The ActiveX plugins are different files from the Fx
> plugins.
> 
> - Is this 'the plugin service using a different field from the plugin' in IE
> vs Fx?
> 
> - As you CAN get the 'Version Number' as 'line two of the Plugin Name' in IE
>     can you use this data for the "Status" column?
> 
> DJ-Leith

The answer to all of these are, short answer yes, longer answer, there is some code that needs to be reworked and yes, it is largely because the code for IE is separate from the code for everything else.

This is in the works but, might take a little longer to actually hit production.
(Assignee)

Comment 4

3 years ago
This is done on production.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.