Thanks Timea for filing this issue; I have reproduced it, and interestingly, the password field on the login page is using
autocomplete="new-password" as Timea noted.
Similarly, QA also found (and I verified) a false positive on the password change form for this site which also uses
autocomplete="new-password" on the "Old Password" field there. Note: to reproduce, you will need a burner e-mail account to sign up for the site, then login and then navigate to the password change form.
This means, on both of these pages, the site is using the semantic HTML markup to indicate the field is a new password field (
autocomplete="new-password"), even though the field is not a new password field.
This is not a bug with the new password model from Bug 1595244 (and its update in Bug 1625601), which only runs when the
autocomplete attribute does not have a value of
"new-password", nor is this a bug with the Password Manager's logic, which displays the password generation option in the autocomplete popup when
autocomplete="new-password". This is a web compatibility issue for the site.
I filed a webcompat issue.