User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112003 Minefield/3.0b2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112003 Minefield/3.0b2pre I think better button names would make easier to users what is happening. Reproducible: Always Steps to Reproduce: Log in to any Web site who is verified (where Firefox can save the password). Actual Results: Message: Do you want Minefield to remember this password? Buttons Remember Never for This Site Expected Results: Message: What do you want Minefield to do with this site password? Buttons: Remember password Don't remember password
Sorry, title should have been: Make Firefox question about entered password clear.
I think the current scheme is pretty clear and the suggested change is too verbose for buttons. If it is just a matter of making things clearer to understand, I think simple "yes" and "no" buttons would suffice. Just answer the question asked in plain english. Again, I will let someone else make this call.
Severity: minor → enhancement
Component: General → Password Manager
QA Contact: general → password.manager
Yes/No/Cancel buttons are way too generic; giving more information inside the buttons lets the user work without reading what Firefox has to say, but understaing what it will do.
I don't think this is a very useful change. It just makes the buttons more verbose, and you got rid of the "never for this site" capability. Semi-related: bug 395038, regarding adding a "not now" button.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX
(In reply to comment #4) > I don't think this is a very useful change. It just makes the buttons more > verbose, and you got rid of the "never for this site" capability. > > Semi-related: bug 395038, regarding adding a "not now" button. > O didn't get rid of it: "Never for This Site" would be "Don't remember password", which says what Firefox will do even if the used does not read the information message.
You need to log in before you can comment on or make changes to this bug.