324411 - Password Manager generates unwanted behaviour in several cases

Status: RESOLVED DUPLICATE of bug 270558

(Toolkit :: Form Manager, defect)

Description

[gigabytesofspam]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

We have been receiving a lot of support calls from customers claiming their user data is not being stored correctly in our profile form. After some thorough testing and debugging it became clear that the behaviour was due to FireFox’s Form Manager which used old/obsolete form values to auto-fillin the form with.

Reproducible: Always

Steps to Reproduce:
An example user path:

1.	the user enters the site and creates a profile with: [e-mail]
2.	the user comes back later and want to update his profile to: [e-mail]

(I used the email form field in my example above; but this behaviour applies to all form fields)
Actual Results:  
the form still contains [e-mail] but the HTML-source shows [e-mail]; the user received an e-mail that his profile was updated to [e-mail] and the database is also updated with the new e-mail address.


Expected Results:  
Obviously an end user expects the form values to match their input.

I don’t know if this is a bug or if it’s a feature; but it definitely is unwated behaviour since it is extremely confusing for the end-user.

Even though form caching can be very helpfull it is unwanted in several cases. I would therefore really like to see one or more of the following options getting implemented in FireFox:
	1. change the Form Managers behaviour so that cached form fields will be updated if a user changes their values in a form
	2. see a HTTP header command introduced to override Form Caching settings: header("Mozilla: No-Form-Cache");
	3. let FireFox show some kind of warning/feedback that the form data shown is based on cached data on the client side

Comment 1

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 270558 ***

Comment 2

[gigabytesofspam]

(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of 270558 ***
> 

I don't know what Manager does what but I would assume that trouble with form data and form caching (ALL form fields; not only passwords) is handled by the Form Manager and not by the Password Manager... 
Are you sure this is a Password Manager bug and if it truly is a duplicate of 270558?