234753 - Two password fields in one form -> no offer to remember

Status: VERIFIED DUPLICATE of bug 209423

(SeaMonkey :: Passwords & Permissions, defect)

Description

[era+mozilla]

User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040123 Debian/1.6-1.he-1

The referenced page has two password fields. The first is actually my library
card number, and it's questionable whether it should really be "input
type=password", but on a general level, it would in fact be nice if this could work.

I confirmed that it will work as expected if I comment out one of the password
fields, or if I change the input type of the library card number field to
something else.


Reproducible: Always
Steps to Reproduce:
1. Visit a page with user name and two password fields
2. Fill it in and submit
3. Do not get any prompt to remember password for this site

Actual Results:  
No prompt to remember password for this site

Expected Results:  
Mozilla should offer to remember my user name and password(s)

Storing a copy of the page on your local disk is not sufficient to repro.
Apparently you will never get a password manager prompt for something stored on
your local disk. If you want to experiment with the page, you need to have it
served to you from another machine.

I looked for other bugs like this one but I couldn't find anything really quite
similar. The underlying architecture should perhaps be revamped so that
passwords and other forms are handled by the same mechanisms, and perhaps by the
same "manager".

Comment 1

[Michiel van Leeuwen (email: mvl+moz@)]

there is a reason for this: usually forms with two passwords are signon forms.
Wallet decides that it doesn't want to store them yet, but only when you logon.

whether this is a good design is open for discussion :)

Comment 2

[era+mozilla]

FWIW the patroninfo page now has only one password field and so cannot be used
to repro.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 6

[Serge Gautherie (:sgautherie)]

V.Duplicate