Closed
Bug 260704
Opened 20 years ago
Closed 20 years ago
Can Uninstall/Update/Disable/Enable an Uninstalled extension
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.7.5
People
(Reporter: ian, Assigned: steffen.wilberg)
References
Details
(Keywords: fixed-aviary1.0, Whiteboard: no trunk checkin yet)
Attachments
(1 file, 2 obsolete files)
|
4.43 KB,
patch
|
bugs
:
review+
bugs
:
approval-aviary+
|
Details | Diff | Splinter Review |
STEPS TO REPRODUCE 0. Install an extension. 1. Uninstall an extension. 2. Without restarting, uninstall it again. EXPECTED RESULTS Step 2 should not be possible. ACTUAL RESULTS Step 2 is possible.
| Assignee | ||
Comment 1•20 years ago
|
||
You can more stupid things, like update, disable, enable (reopen EM to do reenable). Modifying the extensions's preferences is probably okay since it is still active until you restart Firefox.
OS: Windows 2000 → All
Hardware: PC → All
Summary: Can Uninstall an Uninstalled extension → Can Uninstall/Update/Disable/Enable an Uninstalled extension
Version: unspecified → 1.0 Branch
| Assignee | ||
Comment 2•20 years ago
|
||
Working on it.
Assignee: bugs → steffen.wilberg
Target Milestone: --- → Firefox1.0
| Assignee | ||
Comment 3•20 years ago
|
||
Disables cmd_useTheme, cmd_options, cmd_uninstall, cmd_update, cmd_enable and cmd_disable when an item is to be uninstalled. cmd_about and cmd_homepage are still enabled in that case. cmd_reallyEnable only controls whether to show Enable or Disable in the context menu of extensions, so there's no change neeeded there. I also disabled cmd_update when the selected item is to be installed, since the Update dialog doesn't ever finish in that case.
| Assignee | ||
Comment 4•20 years ago
|
||
same as before, but without a stupid change to cmd_about
Attachment #159733 -
Attachment is obsolete: true
| Assignee | ||
Updated•20 years ago
|
Attachment #159736 -
Flags: review?(bugs)
| Assignee | ||
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Whiteboard: [have patch]
Comment 5•20 years ago
|
||
*** Bug 257961 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Flags: blocking-aviary1.0? → blocking-aviary1.0+
| Assignee | ||
Comment 6•20 years ago
|
||
Comment on attachment 159736 [details] [diff] [review] patch v1.1 Bitrotten because of bug 258892.
Attachment #159736 -
Attachment is obsolete: true
Attachment #159736 -
Flags: review?(bugs)
| Assignee | ||
Comment 7•20 years ago
|
||
| Assignee | ||
Updated•20 years ago
|
Attachment #160956 -
Flags: review?(bugs)
Comment 8•20 years ago
|
||
Comment on attachment 160956 [details] [diff] [review] unbitrotten r+a=ben@mozilla.org
Attachment #160956 -
Flags: review?(bugs)
Attachment #160956 -
Flags: review+
Attachment #160956 -
Flags: approval-aviary+
| Assignee | ||
Comment 9•20 years ago
|
||
Checked into branch. Doesn't at all apply on trunk, but that's hardly a surprise.
Status: NEW → RESOLVED
Closed: 20 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
Whiteboard: [have patch] → no trunk checkin yet
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•