Closed
Bug 378658
Opened 18 years ago
Closed 16 years ago
context menu "move to ... again" is disabled
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wsmwk, Unassigned)
Details
version 3.0a1 (20070421)
sometimes the context menu item for "move/copy to <folder> again" is disabled. I don't yet know under what conditions. Restarted in safe mode, the menu item is enabled. Start in normal mode, the menu item is still enabled.
I almost never use the context menu in the thread pane or on a message, so impossible to say when it started - whether it's always been a problem, or a regression or perhaps even due to an extension.
Comment 1•17 years ago
|
||
Wayne,
look into bug https://bugzilla.mozilla.org/show_bug.cgi?id=378623 maybe related to yours.
I don't know if this is related, but "Move Again" no longer shows the folder that is the object of the move. First noticed this in 2.0.0.14. Previously right-clicking showed "Move to folder-name again" where "folder-name was the destination folder. Without showing the folder-name the move-again feature is close to useless.
Reporter | ||
Comment 3•17 years ago
|
||
I don't see comment 3 on trunk.
my problem was always on trunk, so bug 378623/comment 1 might not be relevant - can't say for sure.
Reporter | ||
Comment 4•17 years ago
|
||
still see this. context menu reappears on restart.
note, message|move to xxxxx (again) in command menu is fine.
I don't use branch often enough to confirm comment 2.
confirming, though I still don't know how to recreate.
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #2)
> I don't know if this is related, but "Move Again" no longer shows the folder
> that is the object of the move. First noticed this in 2.0.0.14. Previously
> right-clicking showed "Move to folder-name again" where "folder-name was the
> destination folder. Without showing the folder-name the move-again feature is
> close to useless.
>
In my case it turns out that problem was caused by a bug in the Reminderfox add-on. That Reminderfox bug was corrected and things work as expected again.
Reporter | ||
Comment 6•16 years ago
|
||
I haven't seen this in a long time.
=> WFM
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•