Version: 1.0 (using KDE 3.2 BRANCH >= 20040204, Mandrake Linux Cooker i586 - Cooker) Compiler: gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) OS: Linux (i686) release 2.4.22-10mdk The current version of wallet has a strange save password dialog. The question is a really long version of "Do you want to save the password for this site?" (which is not my point here). My problem is that I can never tell what "Cancel" is supposed to mean. The "Yes" and "Never for this site" are obvious since they answer the question that was posed, but cancel (to me) could mean one of the following. 1. "Cancel" : i.e. I typed in the wrong password, so I want to cancel and type in the correct password. 2. "No" : Don't save the password, but continue. To restate the above statements, I really think the buttons should say "Yes" and "No" especially since nothing is being "Cancelled" and because "No" is really the answer to the question.
I completely agree. The obvious answer is No; Cancel is not at all intuitive. An additional thing I wish to suggest is the layout of the buttons. How about putting Yes and No to one side of the dialog box and 'Never for this site' on the other side of the dialog.. the way Mozilla-Firefox does it.
*** Bug 77739 has been marked as a duplicate of this bug. ***
I was just about to file the same bug...Cancel doesn't fit at all. Actually, I wondered what Cancel did...like if it maybe cancelled the login or something. You're not cancelling anything when you click Cancel...you're just choosing not to store a password. Makes no sense to me.
I was also about to file this bug. I think the best resolution would perhaps be to have two options, "No, Continue"; and "No, Abort Load" (or similar). The second option is not really needed, but since you've prompted the user before submitting, I think you'd better give them the chance of getting out of it if they changed their mind in the meantime.
The current "Cancel" button should be renamed to "No" and a new "Cancel" button added that actually cancels the login attempt.
*** This bug has been marked as a duplicate of 84072 ***