Closed Bug 529298 Opened 16 years ago Closed 8 years ago

Users can install same-version addons multiple times

Categories

(Toolkit :: Add-ons Manager, defect)

1.9.2 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: aakashd, Unassigned)

Details

Build Id: Mozilla/5.0 (Windows; U; Window3sCE 5.2; en-US; rv:1.9.2b4pre) Gecko/20091117 Namoroka/3.6b4pre Fennec/1.0a4pre and Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2b3pre) Gecko/20091117 Firefox/3.6b4pre Fennec/1.0b6pre and Mozilla/5.0 (X11; U; Linux armv6l; Nokia N8xx; en-US; rv:1.9.3a1pre) Gecko/20091117 Firefox/3.7a1pre Fennec/1.0b5 Steps to Reproduce: 1. Install URL Fixer via the Add-ons Manager through a search or the recommended addons list. 2. Restart Fennec. 3. Go to https://addons.mozilla.org/en-US/mobile 4. Click on "Add to Firefox" on the entry for URL Fixer Actual Results: The add-on is downloaded, installed and the Add-ons Manager shows an extension to the grey title box where the restart notification is located. Expected Results: The add-on installation should fail.
Flags: in-litmus?
The bug was originally filed because I was confused as to why a user was able to install the same add-on multiple times. After a discussion with gavin, this is a problem with the edge case that the add-on being installed is the same version as the one that's already installed. That just shouldn't be allowed. We should fail the installation process.
Severity: blocker → normal
Component: General → Add-ons Manager
Product: Fennec → Toolkit
QA Contact: general → add-ons.manager
Summary: Addons Manager: Can install addons multiple times → Users can install same-version addons multiple times
There are plans to have AMO install buttons to indicate if the add-on has been installed or not (which would stop this usecase from ever occurring). For now, as long as the same add-on doesn't get listed multiple times in add-ons manager, I'm okay with wontfix-ing this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.