Version information of plugins should be obvious for users in the Add-ons Manager

RESOLVED INACTIVE

Status

()

RESOLVED INACTIVE
3 years ago
5 months ago

People

(Reporter: philipp, Unassigned)

Tracking

({regression})

40 Branch
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox39 unaffected, firefox40+ wontfix, firefox41+ wontfix, firefox42- affected, firefox43 affected, firefox44 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8627320 [details]
screenshot of missing flash version #.png

As we know unfortunately 0-days for common plugins are not uncommon and in those situations users often get advised to check that they are using the latest version already.
After the aesthetic fix for bug 1161183 has landed, this information for plugins is no longer readily available in the Add-ons Manager - because this information is important for keeping a system updated & secure and for the purposes of support, the version number of a plugin should be surfaced in the main view of the plugins interface again!

Although there is the plugin checker website, it may not always be fed with the latest information available and caused issues by mislabling known vulnerable plugins as up-to-date in the past already (bug 1084537)...
(Reporter)

Updated

3 years ago
Blocks: 1161183
[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]: Regression
status-firefox39: --- → unaffected
status-firefox40: --- → affected
status-firefox41: --- → affected
status-firefox42: --- → affected
tracking-firefox40: --- → ?
tracking-firefox41: --- → ?
tracking-firefox42: --- → ?
Keywords: regression
Same as stated in bug #1175324 comment #7 or another approach will be for Plugins?
Flags: needinfo?(dtownsend)
(Reporter)

Updated

3 years ago
Blocks: 989469

Comment 3

3 years ago
Is this bug a duplicate of bug 1175330? Dave, could you please confirm?
(In reply to Ritu Kothari (:ritu) from comment #3)
> Is this bug a duplicate of bug 1175330? Dave, could you please confirm?

No this is not a duplicate. It is basically bug 1175324 but arguing that plugins are a special case that need the version number. Given that they are updated manually that might be true.
Flags: needinfo?(dtownsend)
Tracked for 40, 41, 42, as Dave's point seems solid to me, as well. Plugin version numbers are useful to the users.
tracking-firefox40: ? → +
tracking-firefox41: ? → +
tracking-firefox42: ? → +

Comment 6

3 years ago
Users being able to easily determine version numbers will help them when they prefer to try posted directions, so I would love for those numbers to be retained.

For SuMo purposes, we really should gather the version numbers automatically so we do not need to ask users to check them. I filed bug 1182904 for that just now.
(Reporter)

Comment 8

3 years ago
any plans to rectify this before it will hit release versions?
Flags: needinfo?(dtownsend)
This is too late for 40. Anyway, not sure it is a big deal as clicking on the module shows the detailed version number.
status-firefox40: affected → wontfix
I don't have the time to work on this right now. I would review a patch to correct it though, should be fairly straightforward just for plugins.
Flags: needinfo?(dtownsend)
Given that there is a workaround to get the version info, this is wontfix for FF41 as it's not a release blocker.
status-firefox41: affected → wontfix
I will stop tracking it as we published two releases with this issue and it is indeed not a big issue.
tracking-firefox42: + → -
(Reporter)

Updated

3 years ago
status-firefox43: --- → affected
status-firefox44: --- → affected

Comment 13

5 months ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.