Closed Bug 1024625 Opened 6 years ago Closed 5 years ago

Improve plugincheck layout to include outdated and unknown plugins


(Plugin Check :: UI, defect, P2)



(Not tracked)



(Reporter: espressive, Assigned: espressive)


Make the distinction on the plugincheck page clear between vulnerable and outdated plugins and do not bundle up to date and outdated together.

Outdated plugins should go under a separate heading stating outdated with a button merely stating 'Update' which will take the user to the download page to get the latest release.

For unknown plugins, add a section at the bottom of the page that is subdued but still lists any plugins that was detected, but which are not tracked in the plugins database.

This will clear up a lot of user confusion and improve the usability and usefulness of plugincheck.
The issue with Java 7 u55, and now Java 7 u65, being reported
by the 'Plugincheck service' as "vulnerable",
when a better report would be "outdated",
is still being seen (and bugzilla bugs are being reported).

In bug 1023835 comment # 6 Schalk Neethling [:espressive] said:
> but, will reference the bug to improve the UI here.

Java 7 u65 reported (2014-06-13). 
In bug 1023835 comment # 7 rml123 at 2014-06-13 01:18:07 PDT wrote:
> Now it has changed to say red button "Update Now" (correct)
> and IS vulnerable (incorrect). However if you are working on a new status
> as a separate issue, for example, green Update Now button with
> status "out of date", then i'm happy to leave this as resolved, thanks ...

Java 7 u65 reported (2014-08-12).
"Java SE7 U65 is displayed as "Insecure" instead of "Outdated" " 
Bug 1052877

Component: → UI
Priority: P3 → P2
Product: Websites → Plugin Check
QA Contact: cbook
Done on production
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.