[false negative] Password generation is not offered for the Register password field on vk.com
Categories
(Toolkit :: Password Manager: Site Compatibility, defect, P3)
Tracking
()
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:
- Go to vk.com and go through the registration flow to reach the password field (requires phone)
- 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()">
Updated•4 years ago
|
Comment 1•4 years ago
|
||
According to its Tranco + Alexa ranking, this site is among the most popular (which we are currently defining to be the top 500).
Comment 2•4 years ago
|
||
Erik is working on a model update to potentially address this.
Comment 3•4 years ago
|
||
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.
Comment 4•4 years ago
|
||
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.
Comment 5•4 years ago
|
||
Assigning severity. Priority-wise we should still get to this sooner rather than later.
Comment 6•4 years ago
•
|
||
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.
Comment 7•4 years ago
|
||
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.
Comment 8•2 years ago
|
||
Moving to P3 as this is not happening in the next release cycle.
Description
•