Closed
Bug 582082
Opened 14 years ago
Closed 14 years ago
Changelog's should be available within the AOM for extensions
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla2.0b3
People
(Reporter: tech4pwd, Assigned: Unfocused)
References
Details
User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100726 Minefield/4.0b3pre Build Identifier: Currently users are blind as to what changes they're installing and/or have installed. Users should be able to access such information from within the Addon Manager. Reproducible: Always
Comment 1•14 years ago
|
||
Blair, is that already part of your patch on bug 562622?
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > Blair, is that already part of your patch on bug 562622? Yes. Not sure if we have another bug for this specifically though.
Comment 3•14 years ago
|
||
I thought so but I can't find it. Lets leave it for now. Whenever we find it, we can dupe.
OS: Windows 7 → All
Hardware: x86 → All
Version: unspecified → Trunk
Assignee | ||
Comment 4•14 years ago
|
||
Fixed with the landing of bug 562622. https://hg.mozilla.org/mozilla-central/rev/488ea306526b
Assignee: nobody → bmcbride
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Flags: in-litmus?
Resolution: --- → FIXED
Comment 5•14 years ago
|
||
So we only fetch the release notes for extension the user is upgrading via the AOM? Do we also have the chance to get those for new installations? Or do we simply not show them right now?
Target Milestone: --- → mozilla2.0b3
Assignee | ||
Comment 6•14 years ago
|
||
(In reply to comment #5) > So we only fetch the release notes for extension the user is upgrading via the > AOM? Yes, and also for all items in the Recent Updates pane. > Do we also have the chance to get those for new installations? Or do we > simply not show them right now? Not for new installs. I don't think it makes sense there, since a changelog isn't that relevant for a new install. But file a bug if you think its worth exploring. Not sure how difficult it would be to add - the UI would be easy, but I don't think the API knows about changelog URLs until it actually finds an update. I think that might be able to be worked around by loading the update.rdf (ie, force a check for an update) and getting the changelog URL for the installed version.
Comment 7•14 years ago
|
||
(In reply to comment #6) > Not for new installs. I don't think it makes sense there, since a changelog > isn't that relevant for a new install. But file a bug if you think its worth > exploring. Well, for some people it can be important. Right now a similar approach has been filed as bug 588740. Means no other bug has to be filed. Verified fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100826 Minefield/4.0b5pre
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Flags: in-litmus? → in-litmus?(vlad.maniac)
Comment 8•13 years ago
|
||
Litmus test added: https://litmus.mozilla.org/show_test.cgi?id=15172
Flags: in-litmus?(vlad.maniac) → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•