Closed
Bug 584348
Opened 14 years ago
Closed 14 years ago
Update add-on button triggers no action on click/tap event
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(fennec2.0b1+)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | 2.0b1+ | --- |
People
(Reporter: vladmaniac, Assigned: mfinkle)
Details
Attachments
(1 file)
6.11 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
Steps: 1. Open Fennec and slide the screen to the left to bring up Options Menu 2. From Options menu select add-on submenu (puzzle icon) 3. Notice the list of installed add-ons and a list of recommended add-ons at the bottom of the content area. 4. Click on the "Update" button at right top of the menu (in the Your Addons sections) ================================================================================ Expected: There should be a list of updates for all installed add-on. If no updates are available, there should be a proper notification to announce that and give some feedback at the press/tap/click on the "Update" button. ================================================================================ Actual: Tapping on "Update" button triggers no action.
Updated•14 years ago
|
OS: Linux → All
Hardware: ARM → All
Assignee | ||
Comment 1•14 years ago
|
||
Sounds like this is a UI issue: You would like some kind of visible confirmation that Fennec checked for updates, but found none. Is this right?
Reporter | ||
Comment 2•14 years ago
|
||
That's right Mark, thanks
Comment 3•14 years ago
|
||
FWIW, I had an old version of Phony 0.2.2, clicked update, and the text appeared saying "A compatibility updated has been applied". So we need text for when there's no update available.
tracking-fennec: --- → ?
Comment 4•14 years ago
|
||
I can confirm this. I had no add-ons installed, only the pre-installed search plugins. Affter pressing the update button, I don't see any indication that anything has happened.
Updated•14 years ago
|
tracking-fennec: ? → 2.0b1+
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → mark.finkle
Reporter | ||
Comment 5•14 years ago
|
||
Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:2.0b2pre) Gecko/20100819 Namoroka/4.0b2pre Fennec/2.0a1pre ================================================================================= Furthermore, Update manager seems to install the same update over and over again, if "update" button is tapped on. Is this expected? I believe it would be nice if previously installed updates would be somehow remembered. Echoed Message: "A compatibility update has been applied"
Comment 6•14 years ago
|
||
A new bug has been filed for the above comment #5. Bug 588867
Assignee | ||
Comment 7•14 years ago
|
||
We don't want to popup an alert. If you have add-ons installed (real add-ons, not the search providers) then you should see some text appear in the row while we look for updates. The search providers are not updatable, so they are ignored. I can make a patch to simply disable the "Update" button if no updatable add-ons are installed.
Assignee | ||
Comment 8•14 years ago
|
||
This patch only enables the "Update" button if an updateable add-on has been installed. During an update check, we change the strings in the add-on rows, so there is a verification that something is happening. The patch also makes some updates to the add-on code: * Adds the new extensions.getAddons.cache.enabled pref * Adds a restart prompt for compatibility updates since the version bump could mean a restart is needed (we check the pendingOperations) * I rename "addon" -> "update" and use the real addon object in the update observer now too. It's less confusing since the object being returned was not a real addon object, just some data related to the update.
Attachment #470902 -
Flags: review?(mbrubeck)
Comment 9•14 years ago
|
||
Comment on attachment 470902 [details] [diff] [review] patch >diff --git a/app/mobile.js b/app/mobile.js >--- a/app/mobile.js >+++ b/app/mobile.js >@@ -170,23 +170,23 @@ pref("extensions.ignoreMTimeChanges", fa >+ if (!anyUpdateable) > document.getElementById("addons-update-all").disabled = true; Do we ever re-enable this button? Hmm, I guess we never need to, since this would only change after installing a new add-on and restarting Fennec. Okay, nevermind. >@@ -594,37 +599,41 @@ var ExtensionsView = { >+ let addon = element.addon; Is this used anywhere? r=mbrubeck with that last question answered.
Attachment #470902 -
Flags: review?(mbrubeck) → review+
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to comment #9) > >@@ -594,37 +599,41 @@ var ExtensionsView = { > >+ let addon = element.addon; > > Is this used anywhere? Yep: > case "compatibility": > statusMsg = strings.getString("addonUpdate.compatibility"); >+ if (addon.pendingOperations & AddonManager.PENDING_INSTALL || addon.pendingOperations & AddonManager.PENDING_UPGRADE) >+ updateable = true;
Assignee | ||
Comment 11•14 years ago
|
||
pushed: http://hg.mozilla.org/mobile-browser/rev/4501ce985781
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 12•14 years ago
|
||
Verified on Build: Mozilla /5.0 (Android;Linux armv7l; rv:2.0b6pre) Gecko/20100903 Firefox/4.0b6pre Fennec /2.0b1pre and Mozilla /5.0 (Maemo;Linux armv7l; rv:2.0b6pre) Gecko/20100903 Firefox/4.0b6pre Fennec /2.0b1pre
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•