Closed
Bug 644044
Opened 13 years ago
Closed 6 years ago
If the file modification time of files in an add-on is in the future then we display that as when it was last updated
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: schneidern, Unassigned)
References
()
Details
Attachments
(1 file)
808.62 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 When I view the Recent Updates pane in the Add-ons Manager, the date listed with the first item ("Easy Youtube Video Downloader 4.0") is "September 25, 2019". The other 3 items in the list are correctly marked as having been updated today ("March 22, 2011"). Reproducible: Always Steps to Reproduce: 1. Open the Add-ons Manager 2. Click "Recent Updates" The problem persists across browser restarts. Actual Results: Date for first item is "September 25, 2019" Expected Results: "March 22, 2011" This is using the Default 4.0 theme (listed as updated "March 22, 2011"). Just a guess, but perhaps this is related to Bug 640302? https://bugzilla.mozilla.org/show_bug.cgi?id=640302
Reporter | ||
Comment 1•13 years ago
|
||
Updated•13 years ago
|
Component: General → Add-ons Manager
Depends on: 640302
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Version: unspecified → Trunk
Comment 2•13 years ago
|
||
A few files in the extension have a file modification date of September 25, 2019 for some reason
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Add-ons Manager shows incorrect (future) date for most recent update of an add-on → If the file modification time of files in an add-on is in the future then we display that as when it was last updated
Comment 3•6 years ago
|
||
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
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•