169760 - Keychain should not replace server-supplied field contents

Status: VERIFIED FIXED

(Camino Graveyard :: HTML Form Controls, defect)

Description

[Martin Stender]

If you tell Chimera to remember, say a value from a login-procedure (where
there's a field named 'username') - the next time Chimera sees an inputfield
with the same name, it displays the previously entered value, even if that
fields value is preset from the server. Its weird, becourse if you look at the
html-source, the right value is there (in this case: "<input type="text"
name="username" size="25" value="martin" disabled>"), but the browser displays
something else, in this case "root", since it remembers that from some db-frontend.

Comment 1

[Greg K.]

Martin, what build ID are you reporting this bug against?

Comment 2

[Martin Stender]

Ver. 0.5 - build 2002091804

Comment 3

[Simon Fraser [no longer active]]

Confirming

Comment 4

[Mike Pinkerton (not reading bugmail)]

would the correct thing here to be to not pre-fill any field with a value
attribute? or would that lead to disaster?

Comment 5

[Mike Pinkerton (not reading bugmail)]

Attachment: testcase

Comment 6

[Mike Pinkerton (not reading bugmail)]

Attachment: test2

test2

Comment 7

[Mike Pinkerton (not reading bugmail)]

so i fixed it to prefill the password only if the value attribute of the
username field matches what we have stored in the keychain. if they don't match,
keep the server supplied value and do nothing with the password field.

the two tests above test this behavior (obviously replace test2 with your
bugzilla username and have a bugzilla password stored in keychain).

fixed.

Comment 8

[Chris Petersen]

Verified in the 2003-01-11-04 NB under 10.2.3. Confirming that if the username
value matches the keychain, the password field is pre filled automatically. If
the  user name isn't the same, then the password field remains blank.