Open Bug 1629916 Opened 4 years ago Updated 2 years ago

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

Categories

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

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

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

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

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

Notes:
Password field:
<input id="join_pass" type="text" class="big_text" value="" onfocus="Join.passTip();" onblur="Join.tipHide();" placeholder="Choose a password" onkeydown="if (event.keyCode == 10 || event.keyCode == 13) { this.blur(); Join.submitPassword(); }" onkeyup="Join.updateStrength()" onpaste="Join.updateStrength()">

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

This is because the <input> there is actually a type=text and never has a type=password variant. This violates our in-app gating condition, so we can't really make it better from the Fathom model.

Thanks for looking into this. If that's the case, then this would either be a site compatibility issue (similar to Bug 1629892) or we could try to make a password field recipe, though I'm not sure if/when those get run currently. Either way, we can take it off your plate.

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 LoginAutoComplete#startSearch was not being hit on this page, meaning our Fathom ruleset was never being executed.

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

Moving to P3 as this is not happening in the next release cycle.

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