Closed
Bug 332264
Opened 19 years ago
Closed 19 years ago
Can't undo move message
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: athomps, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
If you move a message from one folder to another, and then hit Ctrl-Z or do Edit->Undo, it doesn't undo the move, it seems to undo the last action BEFORE the move.
Problem seems to be that the move isn't inserting itself into the Undo chain (or whatever it's called :). Tested this with both drag-and-drop of message and doing Message->Move->pick folder.
Reproducible: Always
Steps to Reproduce:
1. Select one message in a folder.
2. Drag it into a different folder.
3. Hit Ctrl-Z or choose Edit->Undo.
Actual Results:
Last action BEFORE the message move is undone instead - apparently "move" isn't an action in the undo event chain.
Expected Results:
Expected message which was moved to be restored to its original location (i.e., removed from its "new" folder and reinserted into its "old" folder).
It's not a huge priority, but it is something which causes someone to go, "What the heck just happened?" and makes the software look buggy IMO.
Comment 1•19 years ago
|
||
Might be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=59688 but either way, I also would like to undo moving of a message. The last undo seems to stay the last one I deleted, so Ctrl-z un-deletes some other message when I am hoping to un-move a message.
Comment 2•19 years ago
|
||
-> duplicate
(though using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060330 Thunderbird/2.0a1 ID:2006033004 I only seem to be able to reproduce the drag'n'drop case, Message->Move + undo seems to work.)
*** This bug has been marked as a duplicate of 59688 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•