Closed
Bug 128300
Opened 23 years ago
Closed 23 years ago
Password Manager asks to save password after it has just provided the password.
Categories
(SeaMonkey :: Passwords & Permissions, defect)
SeaMonkey
Passwords & Permissions
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 124070
People
(Reporter: pbergsagel, Assigned: morse)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.8+) Gecko/20020227 BuildID: 2002022708 I have encountered a problem with the password mananger at mozillazine. I know this has been reported many times, but I think I have figured how to easily solve it. Also this same issue with the password manager is encountered at other sites. The problem as I encounter it. When a user reads a thread at Mozillazine the password manager fills in the appropriate values. When the user types a message, and clicks on the submit button, the password manger asks if this new password (Its new if the users changed the title for the post) should be saved. This is the wrong behavior. When the password manager has already filled in the values the password manager should not popup again asking for a new password. This generated multiple logins and constantly poping up alert boxes. Reproducible: Always Steps to Reproduce: 1.Have the password manager save a password at Mozillazine. 2.Post a message at Mozillazine. 3.If you inadvertently ask for the pasword to be saved you will store a second password for Mozillazine. Actual Results: Multiple password are saved. Expected Results: I expected only one password to be saved. I am sorry if this is a duplicate bug, but I could not find an exisitng bug report on this. I believe I have a solution (to an issue with the password manager), but do not know the how comples it is to implement or even if it is possible to implement. Here is my solution for the issue detailed above. When a password is stored have the password manager create a pop up window appear listing the fields being stored. Beside the field include a check box indicating if the field can change or never changes: Fields stored Title: "The title of the post." []changable Login: "User Name" []changable Password: ******** []changable [Save Password] [Cancel] This would solve an issue with using the password manager at certian sites (such as chat boards) where one or more fields often changes. The password manager would know that certian fields are changable and not use the changable field to determine if this is a new password and should be saved. In t5he example using Mozillazine the "Title" filed should never be used when determining if this password is new and needs to be saved. Indicating thet the field "Title" is changable allows the password manager to correctly recognize new passwords and will not produce multiple errors. This change would also solve the proble of the password amanager poping up every time a post is made aksing if this password should be stored. (Note: for me this is a major feature, but for others it will be minor. I am listing the severity as major to put this bug on the radar. If others feel the severity level is too high, please lower it.) At Mozillazine the user would check only the box next to Title and not for login or password. Now if the title field changes, the password manager would know this is not a new password and would not ask to save it. But if either the login or password is different the password manager would understand this to be a new password and ask to save it. This would solve the issue of multiple passwords being saved. At Chat boards I am often asked by the password manager which name to use. I am presented with a list all listing the same exact name. I believe this enhancement could solve this. Hioefully this is not a major change and can be considered. (I hope this is not a dup)
Comment 1•23 years ago
|
||
"(I hope this is not a dup)" Heheheheh... Aw man :( I feel your pain, but this kind of stuff with MZine is reported a lot (a little while I was about to but I saw bug 124070). If you want to reopen it because something is different, or you want this to go in a different direction, feel free. *** This bug has been marked as a duplicate of 124070 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•