583544 - Recent Updates pane should not display addons in the application scope

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[Blair McBride [:Unfocused] (UNAVAILABLE)]

Bug 562622 introduces the Recent Updates pane, which currently lists recent  updates for any type of addon. However, its probably not useful to be listing addons that are in the application scope (ie, those shipped with the application), as they will always only update when the application updates.

Note however: If application updates become silent, then maybe its a good thing to list updates from the application as well. Needs discussion.

Comment 1

[Tony Mechelynck [:tonymec]]

IMHO app-global extensions should never be updated automatically, because that installs a second copy (which will never be removed) in the profile. OTOH, getting update notifications for an app-global extension (e.g. Dom Inspector, Javascript Debugger, ChatZilla, which exist at AMO but are also shipped with SeaMonkey) is often more a nuisance than a help. Needs more discussion.

Comment 2

[Blair McBride [:Unfocused] (UNAVAILABLE)]

Note that this isn't about updating them (I don't think we do that), just displaying them as something that was recently updated as the result of an application update.

Comment 3

[Tony Mechelynck [:tonymec]]

Well, this may depend on what kind of build was installed. Users of Release builds probably don't care about app-global addons upgraded together with the app. I use mostly Nightly builds and some time ago (before the New Addons Manager IIRC) I've seen app-global addons mentioned at startup as "updated" if at least one profile-local addon was also updated at the same time; I found it a fun thing, not a nuisance, except that the "These addons have been updated" popup disappeared spontaneously before I had the time to read it all.

Comment 4

[Dave Townsend [:mossop]]

Yeah I agree, we shouldn't be including these in the list. We have an old bug open somewhere that we used to show the default theme as having been installed in certain cases and I am glad it has gone. Let's not re-introduce it.

Comment 5

[BMO Automation]

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.