bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

"OK" - "Cancel" should be "Yes" - "No"

VERIFIED WONTFIX

Status

SeaMonkey
MailNews: Message Display
P3
normal
VERIFIED WONTFIX
18 years ago
14 years ago

People

(Reporter: Henrik Gemal, Assigned: scottputterman)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
After you encounter a problem with copying your mail to the Sent folder you are 
presented with an error saying:
"Your Send operation was successful, but copying the message to your Sent folder 
failed. Would you like to return to the compose window?"

In this dialog there are the "OK" and "Cancel" buttons. But it should have been 
the "Yes" and "No" buttons.

Build 2000060622 on Win2k

Comment 1

18 years ago
putterman, stealing this if you don't mind. i'm sure you have more important 
things on your plate than cosmetic stuff like this, anyways than cosmetic 
things like this.

jglick - do you agree that this is what we should be doing here?
Assignee: putterman → BlakeR1234
Priority: P3 → P4
Target Milestone: --- → M17

Updated

18 years ago
Status: NEW → ASSIGNED

Comment 2

18 years ago
I guess we could just use NetSupportConfirmYN.xul for this

Comment 3

18 years ago
Agree, Yes and No is much preferred over OK and Cancel here.

Comment 4

18 years ago
Yup, agree also.

Updated

18 years ago
Priority: P4 → P1
Target Milestone: M17 → M19

Comment 5

18 years ago
UI guidelines for both Mac OS and Windows say *not* to use `Yes' and `No' as 
button names, and for very good reason: `Your Send operation was successful, but 
copying the message to your Sent folder failed. Would you like to close the 
composition window anyway? ( Yes ) ( No )". Oops.

For just changing the wording, I'd go for `... Would you like to close the 
message anyway?', with ( Return to Message ) in cancel position, and (( Close )) 
in OK position.

But the ideal dialog would probably look roughly like this instead:

+---------------------------------------------------------+
| {mailAppName} ::::::::::::::::::::::::::::::::::::::::::|
+---------------------------------------------------------+
|  .   Your message has been sent, but it could not       |
| /!\  be saved in your "{nameOfUser'sSentFCopiesFolder}" |
| """  folder because {reason, defaulting to `an error    |
|      occurred'}.                                        |
|                                                         |
|      Choose Retry to try saving the message again, or   |
|      Cancel to return to the message.                   |
|                                                         |
|                                  ( Cancel ) (( Retry )) |
+---------------------------------------------------------+

So if the user really wants to close the message, they will return to the message 
and then close it in the usual fashion. That way this dialog can behave 
consistently with (and maybe even share some code with) the dialog which comes up 
when saving a message to the Drafts folder fails.

Comment 6

18 years ago
No time right now.
Assignee: blakeross → putterman
Status: ASSIGNED → NEW
OS: Windows NT → All
Priority: P1 → P3
QA Contact: lchiang → esther
Hardware: PC → All
Target Milestone: M19 → ---
QA Contact: esther → nbaca
If we knew what we wanted here, I think hwaara wouldn't mind doing it?

Comment 8

18 years ago
sure

Comment 9

18 years ago
Agree that this dialog is just bad altogether. Text and available options should 
be changed.  Can we get rid of this bug and fix 28211 instead?  28211 "On Send, 
fail to copy to Sent folder should let users retry, not return to compose 
window."

Comment 10

18 years ago
Marking wontfix, as jglick says, we should fix bug 28211 instead.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 11

18 years ago
ok
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.