Open Bug 406022 Opened 17 years ago Updated 9 years ago

no undo delete message if done in advanced search messages

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

People

(Reporter: wsmwk, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dataloss)

delete message in search messages (imap). not possible to undo the delete. references Bug 383743 – undoing delete of msg in saved search with unread as criteria doesn't restore msg Bug 74567 – Crash on Undo Delete in mail window after del in search ui
Confirmed on linux trunk.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Severity: normal → major
Flags: blocking-thunderbird3?
Keywords: dataloss
Summary: no undo delete message if done in search messages → no undo delete message if done in advanced search messages
dataloss is the reason for requesting blocking - especially because one is now accustomed to having undo work elsewhere in the UI.
speculation as to why undo is not possible in this case?
Severity: major → critical
Either we're not telling the move/copy code to allow undo of this operation, or the undo UI isn't hooked up to the search ui.
Taking in order to keep it on my driving radar; if anyone wants to take a run at this; feel free!
Assignee: nobody → dmose
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Keywords: helpwanted
Target Milestone: --- → Thunderbird 3.0rc1
FYI, Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1b3pre) Gecko/20090121 SeaMonkey/2.0a3pre has the same problem.
Blocks: TB2SM
I don't think this is a blocking item with the new search (bug 474701) providing a much better search that almost replaces this dialog. This bug is still a worthwhile fix, but just won't delay the release of tb3
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
Assignee: dmose → nobody
Keywords: helpwanted
Target Milestone: Thunderbird 3.0rc1 → ---
You need to log in before you can comment on or make changes to this bug.