Closed
Bug 586757
Opened 14 years ago
Closed 14 years ago
No way to uninstall extensions in new add-ons manager
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 478487
People
(Reporter: callow.mark, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4pre) Gecko/20100812 Minefield 4.0b4pre
There appears to be no way to uninstall extensions in the new Mozilla 5 add-ons manager. Only a disable button appears under the enables extensions. In the old add-ons manager on the extensions tab both "disable" and "uninstall" buttons would appear.
I want to be able to uninstall extensions, themes and plug-ins.
Reproducible: Always
Comment 1•14 years ago
|
||
There is a remove button but some extensions can't be removed. Those extensions are systemwide extension that some software outside of FF installed.
Those didn't have a remove button in the old addon manager and they don't have a remove button in the new addon manager.
Plugin also can't be uninstalled because FF didn't install those.
Reporter | ||
Comment 2•14 years ago
|
||
I am running Minefield with a different profile so my normal add-ons do not appear, only the systemwide extensions; not realizing they were systemwide extensions, it seemed to me that there was no uninstall feature.
I would suggest having a greyed-out (disabled) uninstall button for these cases as in the old add-ons manager and have the pop-up help say something like "To uninstall, uninstall the software that installed this extension" and do something similar for plug-ins.
Updated•14 years ago
|
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Comment 3•14 years ago
|
||
Lets get feedback from UX. Jennifer what do you think?
Keywords: uiwanted
Version: unspecified → Trunk
Updated•14 years ago
|
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•