Closed Bug 115338 Opened 24 years ago Closed 24 years ago

Need way to go back from pre-send spellchecking to editing message

Categories

(MailNews Core :: Composition, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 83933

People

(Reporter: rogerd, Assigned: bugzilla)

References

Details

I have my e-mailer configured to spell-check my messages before sending them. Often while spellchecking the message, you will find an error that you need to go back into the editor to fix [e.g. a word has been split by a spurious space and one of the two parts happens to be a valid word by itself so the spellchecker won't let you change it, you accidentally accepted a proposed spelling change to the wrong word (now a valid word, so you can'r get to it with recheck), or you just notices a gramatical, stylistic, or factual error in the message while doing the spellcheck]. The current UI provides no way to do this: the only way you can leave the spellcheck dialog is to click the "Close" button (or the dialog close box), and that always immediately sends whatever the current state of the message is. I have lost count of the number of times this has forced me to send messages that I knew had errors in them. The corresponding feature in Netscape 4.7 didn't do this: you could go back from the pre-send spellcheck to editing the message without being forced to send by clicking the "Stop" button, and this problem is one of the things that most irritates me about moving from 4.7 to 6.X as an email program. What we need is, when doing an automatic spellcheck before sending the message, another button in the dialog that says something like "Stop" "Cancel Send" or "Reedit Message", which closes the spellcheck dialog (accepting all the changes made there so far), but does not send the message, just drops you back into the message composer so you can fix whatever problems. (Once you're done, you resend, and another spellcheck happens - hopefully it won't find anything - before the message is sent.)
Duplicate... looking for original bug.
Bugscape 3581 looks to be the real master of this. Other similar mozilla bug 100388.
QA Contact: sheelar → esther
Right, this is a dup of bugscape 3581. I will close this bug as invalid...
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
Sorry to burst your bubble, but this is NOT a duplicate of Bugscape 3581. 3581 is about clicking Cancel on the sending message progress bar while the message is actually in the process of being sent. This bug is about the previous stage, where you have clicked Send, are in are in the spellchecker for the pre-send spellchecking but have not clicked Close to actually send the message, and then you decide you instead want to go back to the editor - something there is a common need for, that 4.7 used to allow you to do, but that we no longer provide a UI for. This is a UI bug, not a functional bug : 3581 is a functional bug, and is only being kept open until the misleading error message is changed. Surely you are not suggesting that the correct UI for this is to expect the user to click "Close" to trigger the message being sent and then try to immediately "Cancel" before it acually gets sent (which is the only way 3581 would be relevant)?
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
Blocks: 119232
This bug is a dump of bug 83933 and bug 109127. However, those 2 are currently "RESOLVED INVALID" which is no longer a good idea in light of an active development going in the bug 56301
Roger, I'm going to reinflate ducarroz's bubble and quote from bug 3581 in bugscape: Bunch of steps leading up to problem "Results: You receive a Spell Check window, however, if you exit the dialogue by clicking on CLOSE or the X in the upper right corner, the message is sent. Note: This is not how 4.x worked. 4.x had a STOP button, and allowed the user to elect to STOP the Spell Check, and go back into the message to edit (Note:This is how Spell Check performs in 6.0 when you click on the Spell button)." It looks like you've already seen this in http://bugzilla.mozilla.org/show_bug.cgi?id=83933 which I'm going to mark this a dup of. *** This bug has been marked as a duplicate of 83933 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.