Closed Bug 312443 Opened 19 years ago Closed 8 years ago

When updating an extension that is user disabled provide an option to re-enable it.

Categories

(Toolkit :: Add-ons Manager, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: BesTo, Unassigned)

References

Details

(Whiteboard: [intent-to-close])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

1. I dont know if hand-deaktivated extensions will be auto-updated. (Maybee I
should fill a seperate bug.)
2. I deaktivated some extension (cause buggy) by hand and waiting for some
updates. If an update exist - I think so - the extension-manager should ask if
the updated extension should be reaktivated.

Reproducible: Always

Steps to Reproduce:
Summary: ask for activation on update by hand-deaktivated (cause buggy) extensions → When updating an extension that is user disabled provide an option to re-enable it.
(In reply to comment #0)
> 1. I dont know if hand-deaktivated extensions will be auto-updated. (Maybee I
> should fill a seperate bug.)
https://bugzilla.mozilla.org/show_bug.cgi?id=294644#c12
Depends on: 375596
Whiteboard: DUPEME?
I'm inclined to think that when installing (not auto updating) an extension where an old version is installed and disabled then we should just enable the extension. The user has explicitely tried to install it so it should work afterwards.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: DUPEME?
Product: Firefox → Toolkit
Due to a long period of inactivity on this bug (6.11 years), I am intending to close this bug within a month or so in accordance with: https://wiki.mozilla.org/Add-ons/OldBugs Please remove [intent-to-close] from the whiteboard and comment on this bug if you would like to keep it open.
Whiteboard: [intent-to-close]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
See Also: → 1505637
You need to log in before you can comment on or make changes to this bug.