301981 - Show Update History Button for Extensions and Themes

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, enhancement)

Description

[Mike Mason]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050724 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050724 Firefox/1.0+

Can we have a Show Update History button for My Extensions and Themes similar to
the one for Deer Park.

Reproducible: Always

Steps to Reproduce:
1. Go to Tools> Options> Advanced> Update Tab
Actual Results:  
There is not a Show Updates History button in the My Extensions and Themes

Expected Results:  
Give you a Show Updates History button in the My Extensions and Themes

Comment 1

[Steve England [:stevee]]

What use would such a feature be?

Comment 2

[Mike Mason]

I'm of the opinion that knowing what is installed on your computer and when is
always a good thing.
It could also be helpful in identifying what and when a specific version of an
extension is broken.

Comment 3

[Ben Basson]

I have to agree with Steve, I'm not sure I see the value in this. Typically
breakages occur in the following situations:

1. Firefox updates that change core API or code meaning that the extension
   has to be rewritten or changed to accommodate the new version.

2. Extension updates that don't account for cross-platform differences or
   special circumstances.

In the first case, the solution is almost always "get the latest version", which
will solve most cases. The previous history is not relevent to this problem.

In the second case, the problem is newly introduced and a version history isn't
really required to identify the offending update. Since most extensions stick to
specific tasks, users will be able to identify if a common activity worked in
the previous version without such data.

Comment 4

[Ben Turner (not reading bugmail, use the needinfo flag!)]

This has nothing to do with Software Update. It either belongs in EM or in Prefs, but more work will be required in EM...

Rob, what do you think?

Comment 5

[Robert Strong (they/them - no direct email)]

Oops, I get cc'd on [e-mail] so I didn't see this.

I think the value to pain ratio for this is too high on the pain side.

Comment 6

[Tracy Walker [:tracy]]

based on comments and lack of activity since end of 2005, marking wontfix