Closed
Bug 110738
Opened 23 years ago
Closed 22 years ago
Password manager guesses username field incorrectly
Categories
(SeaMonkey :: Passwords & Permissions, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 153986
People
(Reporter: greenrd, Assigned: morse)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5+) Gecko/20011115 BuildID: 2001111512 On the above URL Password Manager thinks that the search field is the "username" field, rather than the library number field. It should be possible to guess correctly, given that the username fields won't tend to be described as "search" fields, and the library number field is right next to the password field. Reproducible: Always Steps to Reproduce: 1. Go to URL above 2. Enter random library card number and password 3. Return to URL 4. Enter another random library card number and password 5. Return to URL Actual Results: Password manager asks you to choose between <> and <> for the username Expected Results: Should ask you to choose between the actual library card numbers you entered.
Assignee | ||
Comment 1•23 years ago
|
||
Password manager doesn't do any screen scraping or use any other sophisticated algorithm for determining user names. Rather it heuristically takes the first textfield to be the "username" by definition. The "username" is just a handle that password manager uses for identifying the form. This heuristic works for the vast majority of login forms. But being a heuristic, it will not work in 100% of the cases. The particular form sited in this bug report is one of the rare cases in which it will not work. My recommendation is simply not to use password manager on this form.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 3•22 years ago
|
||
*** This bug has been marked as a duplicate of 153986 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 22 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
•