Closed Bug 1144572 Opened 10 years ago Closed 10 years ago

Flash upgrade doesn't remove previous version from Add-ons.

Categories

(Firefox :: Untriaged, defect)

36 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: John.Kitz, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150305021524 Steps to reproduce: Upgraded to the latest version of Adobe Shockwave Flash plug-in available. Actual results: Upgrade completed without a hitch. However, upon completion the Firefox Add-ons page shows two versions installed being the current and previous one. So I disabled the previous one on the Add-ons page. Unfortunately this results in both versions being disabled. Expected results: Ideally the previous version ought to have been removed as part of the installation of the newer version, but I'd settle for Firefox allowing me to disable the previous version without automatically disabling the current version as well.
As a work-around one might run Adobe's uninstall tool for Shockwave Flash and reinstall the most recent version of Shockwave Flash, which causes the previous version to be removed from Firefox's Add-on page.
It's possible that you have 2 Flash versions active on your system if you upgrade the flash version. Firefox should use always the latest and newest one so there is no security issue. The old Flash version is cleaned up by the Adobe installer if you reboot your system and if that doesn't happen you would have to report that to Adobe. I do not see a bug here so I have to mark this report invalid
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
The way Firefox's code has been designed and written may result in the latest version of an add-on being used, but when it is impossible to deactivate one of two versions of an add-on installed it's impossible for an end user to determine which version is active. Judging by the number of hits resulting from my Google search for this topic it might be worthwhile reconsidering.
You need to log in before you can comment on or make changes to this bug.