User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401 I received an email to which I wanted to respond. I did not select compose but instead acted as if I could respond to the email itself. I rubberbanded the first part of the text and pressed the delete key. Well, hells bells, the text of the email I had received and rubberbanded was DELETED. It was GONE. This should NOT happen!! Reproducible: Always Steps to Reproduce: 1.Rubberband text in original email. 2.Press the Delete Key. Actual Results: Text is permanently gone from received email. Expected Results: Text in original email should not be editable. It should not be possible to edit contents of a received email.

sorry, I'm not a native speaker but what is "rubberbanded" ? If you select text in a received mail and you press the delete key, you wil delete the whole mail. and please retest with a recent build because you use 1.4a and we accept only busg from the latest milestone (which is 1.5b)

No response (why a mail bug ended up in Browser-General is beyond me). If you have further (and reproducible information, especially what 'rubberbanded' means), please comment further in this bug.

Reopening. Gene and I have discussed this over e-mail, and I've got a clear picture of what he's saying. When we set the focus ring in Mail to the message body, it's VERY easy to accidentally delete the message (DEL is still an active command/key in this view). He's asking that we change this behavior, making it so we only accept delete in the stand-alone message window, which is a great point. Confirming the bug, setting to enhancement (to pick up RFE status), and sliding over to the Mail component. Gene, thanks for your patience and understanding in working with me on this request.

Confirming bug.

The message should be still in the trash unless you use shift+delete or Imap with "delete it immideately" This would also break 90539

MASS-CHANGE: 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