Open Bug 1629920 Opened 4 years ago Updated 4 years ago

[False Negative] Password generation is not offered for the password field on change form


(Toolkit :: Password Manager: Site Compatibility, defect, P2)




Tracking Status
firefox75 --- disabled
firefox76 --- affected
firefox77 --- affected


(Reporter: tbabos, Unassigned)


(Blocks 1 open bug, )


(Whiteboard: [passwords:generation])

Affected Versions:
Nightly 77.0a1 (2020-04-14) (64-bit)
Beta 76.0b4

Affected Platforms:
Windows 7/10 x64
MacOS 10.14
Ubuntu 18.04

Steps to reproduce:

  1. Go to and reach the Change Password
    credentials to test this: pass: NicoKlaus#123
  2. Click on the New Password and Retype Password fields

Expected Result:
The autocomplete dropdown should display the Password Generation option for both password fields

Actual Result:
Password Generation was not offered for password fields

Not a regression of this implementation, it can also be reproduced in Release 75

<input class="_58al _2gnb" type="password" aria-errormessage="js_ha" aria-invalid="true" aria-labelledby="js_h8" autocomplete="disable_autocomplete" id="js_h7" value="">

This does not happen for all Facebook accounts (different Facebook interface?) but it is 100% repro with the credentials given in steps

Whiteboard: [passwords:generation]

According to its Tranco + Alexa ranking, this site is among the most popular (which we are currently defining to be the top 500).

Priority: -- → P1

Erik is working on a model update to potentially address this.

Assignee: nobody → erik
See Also: → 1631818
Assignee: erik → nobody

Assigning severity. Priority-wise we should still get to this sooner rather than later.

Severity: -- → S3

When testing the model update in bug 1638187 I found that the "new password" field was not being recognized (score: 0.3350142757914845) while "re-type password" was (score: 0.7748064545910444).

It's worth noting that this is a live page, though, and these results have been somewhat flaky.

Bumping down to P2 since although this is a popular website, the issue is a false negative, not a false positive and the user can use the context menu as a fallback.

Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.