Closed
Bug 320180
Opened 20 years ago
Closed 2 years ago
closing compose window during send should save draft
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mikel, Unassigned)
References
Details
(Keywords: dataloss, Whiteboard: [closeme 2024-05-01])
I composed a new message, clicked on Send, then for some reason the window got stuck saying "Sending message...". I presume there was a network problem talking to my SMTP server.
I clicked on the close window [x] button (or was it the Cancel... button on the send dialog?) and got two options: Wait or Quit.
Clicking Wait wasn't going to help since it had been trying for about 4 minutes, so I clicked Quit.
Now my message was neither sent, stored in the Sent folder on my IMAP server, or stored in the Drafts folder on my IMAP server. Apparently the message I had composed but not successfully sent is now gone.
| Reporter | ||
Comment 1•20 years ago
|
||
(It wasn't in any of Unsent, Drafts, or Sent in Local Folders, either.)
Comment 2•20 years ago
|
||
There is an important difference in behavior depending on whether you have the send-progress dialog enabled or not (mailnews.show_send_progress), and I also see a slight difference in behavior across the recent versions.
If show_send_progress is True, and you cancel transmission using the dialog's Cancel button, you still get the bogus error message (bug 120278), but the compose window is not closed; you can save as a draft, or retransmit, from that point.
If show_send_progress is True but you close the compose window while sending, transmission continues (via the progress dialog) despite the Wait/Quit prompt being displayed. I think the progress dialog should be a modal child of the compose window, preventing this instance; but I think that's a separate bug
from this one.
If show_send_progress if False, then cancelling transmission by clicking the
[X] widget shows Wait/Quit as described; after Quit is clicked, here's where I see differences, which might be due to software changes or might be due to the state of the program at the time I tested.
* With TB 1.5, after clicking Quit, there were no windows left in evidence
(besides the 3-pane)
* With TB 2a1-0523, after clicking Quit, a new *blank* compose window was
opened, which has disabled address widgets and subject field (bug 127565 /
bug 129290). As noted at 129290, this might be a timing issue depending on
when the [X] is clicked; it might also apply to Cancel from the progress
dialog. The disabled compose window can be closed without a problem.
* TB 3a1-0529 behaved as 2a1 -- but, in this case, when I closed the disabled
compose window, the entire program shut down!
Assignee: mscott → nobody
Component: Message Compose Window → MailNews: Composition
OS: Windows 2000 → All
Product: Thunderbird → Core
QA Contact: composition
Hardware: PC → All
Version: 1.5 → Trunk
Comment 3•20 years ago
|
||
*** Bug 305582 has been marked as a duplicate of this bug. ***
| Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
Comment 6•2 years ago
|
||
Do you still encounter this problem?
Flags: needinfo?(mikel)
Whiteboard: [dupeme?] → [closeme 2024-05-01]
Resolved per whiteboard
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(mikel)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•