For addons that can't be updated, need to indicate this somehow.

RESOLVED INACTIVE

Status

()

defect
RESOLVED INACTIVE
9 years ago
a year ago

People

(Reporter: Unfocused, Assigned: jboriss)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rewrite])

Some addons can't be updated - for example, they are installed outside of a Firefox profile. Need to be able to indicate that updates will *not* be checked for.
We should check for updates as long the user has write permissions for those folders, or?
(In reply to comment #1)
> We should check for updates as long the user has write permissions for those
> folders, or?

Yea, AFAIK, the API checks for updates for anything that can potentially be updated. It's not just write permissions - some addons may not have an update check URL, or a provider may not support checking for updates (eg, the lightweight themes provider). Just need some indication in the UI that come items are not able to be updated, ever.
(In reply to comment #2)
> check URL, or a provider may not support checking for updates (eg, the
> lightweight themes provider). Just need some indication in the UI that come
> items are not able to be updated, ever.

Oh, there is no way to check for updates of a personas and it's something we don't wanna do in the future?
(In reply to comment #3)
> Oh, there is no way to check for updates of a personas and it's something we
> don't wanna do in the future?

AFAIK, no. They're not expected to change over time. Although I think there may be some cases where it will re-download the image, because its no longer cached for whatever reason - but that will always happen transparently in the background.
Note to self: Just need to check for the PERM_CAN_UPGRADE permission.
(Assignee)

Updated

9 years ago
Blocks: 598738
Assignee: nobody → jboriss
Keywords: uiwanted

Comment 6

a year 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
Last Resolved: a year ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.