Open Bug 1782387 Opened 3 years ago Updated 3 years ago

Password manager does not unfolds correctly for username

Categories

(Toolkit :: Password Manager, defect, P3)

Firefox 102
defect

Tracking

()

UNCONFIRMED

People

(Reporter: yonatan.el.amigo, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

Every time I go to login to online banking, I am forced to type in the username because the password manager doesn't seem to be working right here.
Website: https://bdvenlinea.banvenez.com/

Actual results:

Currently the password manager does not unfolds the username in the input box for the user name.

But if you do it right pair the input box for passwords.

Expected results:

The browser should display a list of usernames stored in the password manager to populate the username input box.

I have tried in another browser (such as Chrome) and everything works fine, so it is a specific problem with firefox apparently.

The Bugbug bot thinks this bug should belong to the 'Toolkit::Password Manager' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Password Manager
Product: Firefox → Toolkit

Checking if this.#isProbablyAUsernameLoginForm returns false. The input element is not categorized as username Field.

<input id="mat-input-0" class="mat-input-element mat-fo… ng-pristine ng-invalid" _ngcontent-c10="" aria-label="usuario" autocomplete="off" formcontrolname="username" matinput="" maxlength="16" minlength="6" oncut="return false" tabindex="1" type="text" aria-invalid="false" aria-required="false">

Nor is the formElement categorized as login form.

<form class="ng-untouched ng-pristine ng-invalid" _ngcontent-c10="" novalidate="">

(In reply to Janika Neuberger (:jneuberger) from comment #2)

Checking if this.#isProbablyAUsernameLoginForm returns false. The input element is not categorized as username Field.

<input id="mat-input-0" class="mat-input-element mat-fo… ng-pristine ng-invalid" _ngcontent-c10="" aria-label="usuario" autocomplete="off" formcontrolname="username" matinput="" maxlength="16" minlength="6" oncut="return false" tabindex="1" type="text" aria-invalid="false" aria-required="false">

Nor is the formElement categorized as login form.

<form class="ng-untouched ng-pristine ng-invalid" _ngcontent-c10="" novalidate="">

Somehow the Chrome guys manage to get this to work.

[img]https://raw.githubusercontent.com/Yona-TYT/imgs/081c2bc9825b329ca669c9ecd191ab7e94efae6e/Screenshot_20220802-065114.jpeg[/img]

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

Attachment

General

Created:
Updated:
Size: