202949 - Mozilla needs the ability to delete a password field if the password manager stores several fields

Status: RESOLVED EXPIRED

(SeaMonkey :: Passwords & Permissions, defect)

Description

[Simon Spiegel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030411 Phoenix/0.5+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030411 Phoenix/0.5+

For my online banking (see URL) I need both my personal password and short
password ("Passwort Zusatz") which changes every time. I have this second short
password on a list my bank has given me and every time I use one I have to erase
it. This additional security measure doesn't work properly with Mozilla since
Moz saves both passwords. So every time I want to login into the bank all fields
are prefilled although I don't want the last field to be because it changes
every time.

Reproducible: Always

Steps to Reproduce:
1. Enter username, password and additional password ("Passwort Zusatz")
2. Login
3. Logout
4. Login agian.

Actual Results:  
"Passwort Zusatz" is prefilled.

Expected Results:  
"Passwort Zusatz" should be empty.

I know most of you wont be able to test this with my URL since you don't have an
account on that bank but I'm sure other banks work the same way.

Comment 1

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420