After Add-ons update process is completed, Recent Updates pane should be automatically refresh. Steps: 1. Install an outdated extension version 2. Restart the browser, and as soon as possible to open the Add-ons Manager -> Recent Updates pane 3. Click the gear icon, and then click Check for Updates Wait for the text prompts the update is complete, at this time the panel without change, until you close and re-open the panel.
Component: Microsummaries → Add-ons Manager
OS: Windows 7 → All
Product: Firefox → Toolkit
Hardware: x86 → All
Version: unspecified → Trunk
So there is no text displayed after an extension is updated? Did I understand correctly and can you reproduce reliably? FTR, this works fine for me - updated No Script extension and didn't spot any problems in Nightly.
Created attachment 668707 [details] screen slideshow Sorry, I describe the steps are not clear enough and correct. I refer to before update the extension of did not appear in the Recent Updates panel, after the update has not been added to the pane. See the screen slideshow
I get what you mean now. I can confirm this. Not easy to test, because installing an add-on automatically lists it in Recent Updates for 2 days. Can't select the timespan due to bug 583534. If I install an older Adblock+ (non-restartless), the extension in listed in the Recent Updates Pane and checking for updates correctly shows the Restart now message. Haven't tried without anything listed in the Recent Updates pane though.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Install an older version of the extension (Fully installed, may need to restart), then close Firefox, use FileMenu Tools (for Windows) or 'touch' command (for Linux) to change modified time of the extension .xpi file in [Profiles folder]/extensions directory, change the modified date to a year ago. Run Firefox, it no longer appears in the Recent Updates pane, can then be test.
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: a day ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.