Closed
Bug 481893
Opened 16 years ago
Closed 16 years ago
Sandbox Addon should notify (not autoupdate) of update available
Categories
(addons.mozilla.org Graveyard :: Administration, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 375359
People
(Reporter: slamdunkinpool, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/530.1 (KHTML, like Gecko) Chrome/2.0.166.1 Safari/530.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
A user with experimental addon never get notified of updated version of the addon. Its unsafe to auto-update experimental addon but there should be a way to tell the user that there is a new version available. Currently the user will have to manually visit AMO and search for the addon to find out if a newer version is available.
A notification (with small warning) of update availability should be safe.
See additional comments supporting this https://bugzilla.mozilla.org/show_bug.cgi?id=375359#c9
Reproducible: Always
Steps to Reproduce:
1. Login to AMO
2. Install experimental addon (the one authored by you)
3. Increment the version of experimental addon.
4. In browser Tools->Addons->Find Updates
Actual Results:
No updates were found.
Expected Results:
A message should be displayed that update for an experimental addon is available.
When I check the dashboard-statistics of my addon(experimental and never public released), I find that people are still using old version of my addon even though I have updated the version 5-6 times and have added many new features. Plus fixed some bugs.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 2•16 years ago
|
||
I resolved this as a dupe although it's just talking about notification. We can reopen if you like, but it would be a Firefox bug, not AMO.
Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•