Closed
Bug 305582
Opened 19 years ago
Closed 19 years ago
missing cancel message sending possibility when send progress dialog is not used
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 320180
People
(Reporter: moixa, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 When not using the default (see bug 218557) send progress dialog it is not possible to cancel the sending of a message without loosing that message. Reproducible: Always Steps to Reproduce: 1. Disable send progress dialog: user_pref("mailnews.show_send_progress", false); 2. Block outgoing SMTP traffic to have a long delay when sending message 3. Compose new message, press "Send" Actual Results: Message window tries to send and waits for SMTP timeout. There is no possibility to cancel the sending except for closing the window upon which the dialog "Mail is currently in the process of sending a message." with "Quit" (leave and _loose_ message) and "Wait" (for long SMTP timeout) button. Expected Results: Message window tries to connect and wait for SMTP timeout. After pressing Alt-F4 the dialog pops up: "Mail is currently in the process of sending a message." Dialog has three buttons: "Quit message" (leave and loose message), "Wait" (wait for SMTP timeout) and "Cancel sending" (only cancel sending and go back to editing mode).
| Reporter | ||
Comment 2•19 years ago
|
||
Couln't decide between major (dataloss as I loose my message, when clicking Quit) and enhancement (can wait for the timeout (which somehow though is freakin' long)), so I settled for normal as compromise..
Comment 3•19 years ago
|
||
Duping this to a bug that I thought described the problem better -- which is flagged 'dataloss'. *** This bug has been marked as a duplicate of 320180 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•