Open Bug 1629912 Opened 8 months ago Updated 6 months ago

[false negative] Password generation is not offered for the Register password fields on twitter.com

Categories

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

Desktop
All
defect

Tracking

()

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

People

(Reporter: tbabos, Unassigned)

References

(Blocks 1 open bug, )

Details

(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 twitter.com and go through the registration flow to reach the password field
  2. Click on the Password field

Expected Result:
The autocomplete dropdown should display the Password Generation option

Actual Result:
Password Generation was not offered for the Password field

Regression-Range:
Not a regression of this implementation, it also doesn't work in Beta 75

Notes:
Password field:
<input autocapitalize="sentences" autocomplete="on" autocorrect="on" name="password" spellcheck="true" type="password" dir="auto" data-focusable="true" class="r-30o5oe r-1niwhzg r-17gur6a r-1yadl64 r-deolkf r-homxoj r-poiln3 r-7cikom r-1ny4l3l r-1inuy60 r-utggzx r-vmopo1 r-1w50u8q r-1swcuj1 r-1dz5y72 r-1ttztb7 r-13qz1uu" value="">

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
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 password field was not being recognized (score: 0.04266685751028965).

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

This was added to the model samples.

You need to log in before you can comment on or make changes to this bug.