Password field forgets value attribute when changing content after using keyboard navigation

RESOLVED WORKSFORME

Status

()

Firefox
General
--
critical
RESOLVED WORKSFORME
13 years ago
13 years ago

People

(Reporter: marcel, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

What happens is that when a password field has a value and the user goes to the
next field. When the user comes back to the password field using keyboard
navigation (SHIFT-TAB) and deletes the last character (navigate to the last
character using the arrow keys) the value of the field will be empty. From that
moment on, the characters that where already typed are inaccessible by script.

Example code:
<form target="_blank">
   <fieldset>
     <legend>Forms example</legend>
     <p>
       <input type="password" name="password"
         onchange="alert(this.value)"/>
       <label>Password</label>
     </p>
     <p>
       <input type="text" name="name"/>
       <label>Name</label>
     </p>
   </fieldset>
</form>

Reproducible: Always

Steps to Reproduce:
1.Enter the value 'abc' in the first password field
2.Leave the field using the TAB key
3.After clicking the alert with the value 'abc' away, navigate back to the first
field using 'SHIFT+TAB'
4.Press the RIGHT ARROW key to go to the last entry location
5.Delete the last character 
6.Press TAB again
Actual Results:  
The result is an empty alert

Expected Results:  
The alert should have displayed the password characters present at that time ('ab')
Created attachment 192884 [details]
Test html file as described by reporter

From reporter's description of the bug
WORKSFORME with 20050816 build on WinXP Pro SP2.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.