101111 - Dragging a message into Desktop Trash does not result in deleting message

Status: RESOLVED DUPLICATE of bug 70776

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Dagwood Reeves]

Dragging a message into the Desktop Trash does not result in deleting message,
as it should.  Instead, a document titled "untitled clipping" will appear in the
Trash and the message remains undeleted.

Steps to reproduce:

1. Drag a message from the message list pane into the OS Trash.

Comment 1

[laurel]

I don't see  that we ever had this behavior in 4.x and have never heard anyone
talk about implementing it(moz or nscp).

Comment 2

[Greg K.]

Confirming as an RFE. Leaving up to assignee whether or not to mark WONTFIX.

Though Nav 4 didn't do this, some other Mac applications do.

If this were implemented, what would happen is that a drag of a given message to the 
Desktop Trash would result in the Delete action being performed on that message, the 
actual Delete action being defined on a per-account basis.

Comment 3

[Mike Gratton]

See also: bug 74937, bug 70776, bug 76629.

Comment 4

[Mike Gratton]

Eh, ignore bug 74937 in the list above. Sorry.

Comment 5

[Robert Kaiser]

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

Comment 6

[Robert Kaiser]

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