Not sure if I got the right "Component"... Mozilla has a very nice feature (I think it's new...) where it saves the username and password for login sites. It works well, but one of the confirmation dialogs is worded in a confusing manner: ------------------------------------------------------------------------ Confirmation Dialog Do you want to save the username and password contained on this form? [X] If not, do you want to remember this decision? [ OK ] [ Cancel ] ------------------------------------------------------------------------ It's very unclear what's going on here. I have no idea what the check box is supposed to do. If I understand the purpose of this dialog box, might something like this be clearer: ------------------------------------------------------------------------ Confirmation Dialog Do you want to save the username and password for this form? [ ] Do not ask when viewing this page in the future. [ OK ] [ Cancel ] ------------------------------------------------------------------------ or even: ------------------------------------------------------------------------ Confirmation Dialog Do you want to save the username and password for this form? [ Yes ] [ Skip ] [ Never ] [ Help ] ------------------------------------------------------------------------

giving to dp

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

Good suggestion. However, the wording cannot be "Do not ask when viewing this page in the future" because we must always ask if the user says he wants to save it (otherwise we would have a security breach on a machine in a shared environment). So the wording on the second message will be changed to "Never save when viewing this page in the future."

will verify when the UI is available

While attempting to verify this bug, I noticed that the statement in question no longer exists (the part about never saving). Is this part no longer relevant? Or are we just no longer asking, or...

If the user logs into a site and doesn't want us to save his password, he probably never wants his password saved for that site. So once he gives a negative answer we will automatically remember it for that site. This avoids the confusing checkbox and simplifies the user's experience. This might have been a bad decision and perhaps we should resurect the checkbox with the wording "Never save for this site". This is what is currently done for wallet. Still a bit confusing because if the checkbox is checked and he presses OK we ignore the checkbox since it's a meaningless combination (how could he say "never save for this site" but at the same time be saying "save it this time"). If you think we should resurect the checkbox (at the very least it will be consistent with wallet), then reopen this bug report. The change in the code is trivial.

I think a simple user experience is better, probably. What are the odds that a user could delete a site from the 'Don't Remember List' using the Display Signon Viewer?

Your question is ambiguous. Are you asking the odds that we can implement the signon viewer to have this ability or the odds that the user is savvy enough to use the signon viewer? If the former, this was completed long ago (but of course you can't use it yet until pollmann or brendan fix the blocking bug that is currently making the tabs inoperable). If the latter, then ask German that question.

The former was my question. Since this will eventually be implemented once the blocker bug is fixed, marking verified. Thanks.

Just to clarify. It will not "eventually be implemented" -- it is implemented now. As soon as the bug is fixed you will be able to see it.

ah, semantics

Bulk move to Single Signon component, which has subsumed Password Cache.