can't remove "disabled" extension after upgrading to a nightly that breaks that extension

RESOLVED WONTFIX

Status

()

defect
RESOLVED WONTFIX
6 years ago
a year ago

People

(Reporter: pomax, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: dupeme)

(Reporter)

Description

6 years ago
Upgrading to the new nightly (with australit) has disabled an extension, without the option to remove it since it's now useless. Even if disabled, it kind of makes sense to offer people the option to remove.

I'm pretty sure this was already the case in previous versions, I just ran into it now, and it's kind of annoying. Dead weight is dead.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 640775
Sorry, wrong dupe. So, the bug here is that it's not possible the remove an add-on that has been disabled and can't be enabled. There is probably a dupe for this somewhere.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Whiteboard: dupeme
Pomax: Is your issue that the add-on wasn't automatically removed, or that you can't remove it yourself through about:addons?

We don't automatically remove the add-on, because it's possible for the author to release a new, compatible version in the future and then (if you have automatic add-on updates enabled, which is the default) we'll upgrade and re-enable it.
Mass-closing old Extension Compatibility bugs that relate to legacy add-ons or NPAPI plug-ins. If you think this bug is still valid, please reopen or comment.

Sorry for the bug spam, and happy Friday!
Status: REOPENED → RESOLVED
Last Resolved: 6 years agoa year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.