Closed Bug 69992 Opened 24 years ago Closed 14 years ago

"Undo Delete Message" doesn't show until selecting another folder or Get Msg for "Remove it immediately" mode

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: nbaca, Unassigned)

Details

Build 2001-02-19-08: NT4
Haven't tried Linux or Mac

Overview: Using the "Remove it immediately" trash model, if a message is deleted 
and you try to Undo the action it will not bring the message back. In 4.x the 
message did reappear.

Steps to reproduce:
1. Go into the Server Settings panel and set the trash model to "Remove it 
immediately".
2. Delete a message
3. Select Edit|Undo Delete Message

Actual Results: The message did not reappear.
Expected Results: I expected the message to reappear.
QA Contact: esther → huang
Marking nsbeta1 because I think it would be a good idea to have atleast a first 
level undo option.
Keywords: nsbeta1
I believe this is invalid. 
Delete immediately in 4.x is listed as "can't undo this operation", so if it did
undo in 4.x that was probably not intentional behavior.
Nevermind, I was thinking wrong... at one time I thought we had no Undo on
delete immediately, but I see it's listed in prefs as CAN be restored by Undo.
Actually, this is working for me with feb22 commercial trunk and Win98, although
the undo doesn't show until you select another folder and come back or Get Msg
again.
Based on Laurel & my testing:
Updating the summary from "Undo Delete Message doesn't work with Delete 
Immediately trash model" to "Undo Delete Message doesn't show until selecting 
another folder or Get Msg for Remove it immediately mode".
Summary: "Undo Delete Message" doesn't work with Delete Immediately trash model → "Undo Delete Message" doesn't show until selecting another folder or Get Msg for "Remove it immediately" mode
marking nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Target Milestone: --- → Future
Just wanted yto revieve this one as i miss this feature now that i have started
to use mozilla as my defaut mail client. 

In NS 4.x when you were viewing a message in a new window or even in 3-pane
view, and if you deleted it, you could press Ctrl+Z and get the message back in
the folder and in the active view window. And if you kept going Ctrl+Z, you kept
getting deleted messages back in the folder and in view to.

Try it .. and you will see what i mean and how useful it is if you delete
something and what to see it immediately! In the days of SPAM.. this is a must
feature!

And before i close..  thank you all for mozilla!.. God Bless you! ;-)
See also bug 132121, Can't undo shift delete of local messages.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: huang → message-display
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Invalid. Delete immediately just means that.
Resolution: EXPIRED → INVALID
You need to log in before you can comment on or make changes to this bug.