Bug 1571719 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

**Note**
* 

**Affected versions**
* version1

**Affected platforms**
* platform1

**Steps to reproduce**
1. Open browser.
2. Go to the google registration page.
3. Generate a password in the password field.
Observe: The characters are not masked when the field is focused.
4. Delete the generated password.
5. Input a new password.

**Expected result**
*  The password is masked while being written.

**Actual result**
*  The password is NOT masked while being written.

**Additional notes**
* This issue may be fixed by the fix of bug 1571465, depending how it gets fixed.
**Note**
* The password field remains unmasked if the user erases the generated password and inputs his own string

**Affected versions**
* version1

**Affected platforms**
* platform1

**Steps to reproduce**
1. Open browser.
2. Go to the google registration page.
3. Generate a password in the password field.
Observe: The characters are not masked when the field is focused.
4. Delete the generated password.
5. Input a new password.

**Expected result**
*  The password is masked while being written.

**Actual result**
*  The password is NOT masked while being written.

**Additional notes**
* This issue may be fixed by the fix of bug 1571465, depending on how it gets fixed.
**Note**
* The password field remains unmasked if the user erases the generated password and inputs his own string

**Affected versions**
* Nightly v70.0a1

**Affected platforms**
* All

**Steps to reproduce**
1. Open browser.
2. Go to the google registration page.
3. Generate a password in the password field.
Observe: The characters are not masked when the field is focused.
4. Delete the generated password.
5. Input a new password.

**Expected result**
*  The password is masked while being written.

**Actual result**
*  The password is NOT masked while being written.

**Additional notes**
* This issue may be fixed by the fix of bug 1571465, depending on how it gets fixed.

Back to Bug 1571719 Comment 0