1800275 - Cannot autofill password with Wells Fargo site

Status: NEW

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

Description

[David]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

Login to Wells Fargo banking site which i do on a daily basis

Actual results:

Firefox cannot populate password field - This functionality has worked for many years, and the same functionality works using latest version of Chrome.

Windows 11, Firefox version is: 106.0.5, possible this was introduced as a bug in the latest version.

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Expected results:

Firefox is able to successfully populate the password field

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 2

[Dimi Lee [:dimi]]

Hi David,
Thank you for reporting the bug! I cannot reproduce this issue on Fx106 release and Fx108 nightly.
So I would like to confirm:

1. Are you referring to the sign-in page of https://www.wellsfargo.com/
2. Do you mean after navigating to the website, Firefox autofills the username field, but not the password field?
   Thanks!

Comment 3

[David]

Yes, Wellsfargo.com, ID/Password signin, UserdID is prefilled and password field is empty, click on empty password field and Firefox displays dropdown list with IDs, click on ID to prefill password and nothing happens, password field is still empty.

This has worked for many years and continues to work with Chrome. But not with Firefox v106.0.5.

Comment 4

[David]

Also tested on v107 updated today, this is occurring on Windows 11 in case that fact is pertinent. As stated earlier, this just started recently and has worked fine for many years, and also works using the same site with Chrome where the password is prefilled successfully.

If you are in a position to troubleshoot this and work on a fix, I can spend some effort to retest with an earlier version of Firefox ......

Comment 5

[David]

Additional:

I have discovered that if I press the "delete" key prior to executing the usual steps to invoke the password prefill (click to display the dropdown list and then select the ID associated with the password), the password is prefilled successfully - However, this was not necessary until just recently and is not needed for Chrome to successfully prefill the password field for this site. Also Chrome populates the password field immediately when the page is displayed based on the Userid being saved by the web page whereas with Firefox additional keystrokes are needed to fill the password field, so they do work differently.

This may be the result of a change to the web page by Wells Fargo since banks are always tweaking their security, but it seems that Firefox should be better at handling this situation. I also don't understand why Firefox can't just fill the password field when the page is displayed (like
Chrome) since the Userid is saved and prefilled by the web page - If the Userid is present and there is a password associated with this ID and this web site, just prefill the password.

Comment 6

[Dimi Lee [:dimi]]

Hi David, thank you for the quick reply!
I can't still reproduce this bug on my platform, could you help record a short video (include both no prefilled after navigating to the page and not filled after selecting the id via the dropdown list) so I can see what the difference is? thanks!

Comment 7

[David]

Attachment: ScreenCaptureProject23.mkv

Comment 8

[David]

(In reply to Dimi Lee [:dimi][:dlee] from comment #6)

Hi David, thank you for the quick reply!
I can't still reproduce this bug on my platform, could you help record a short video (include both no prefilled after navigating to the page and not filled after selecting the id via the dropdown list) so I can see what the difference is? thanks!

I added the video you requested. Between the 3rd and 4th click on the dropdown box in the video, the "delete" key is pressed once.

Comment 9

[David]

F Y I - I have also reproduced this condition on a 2nd computer running Windows 7, using the same Wells Fargo link and Firefox v107

Comment 10

[Dimi Lee [:dimi]]

(In reply to David from comment #9)

F Y I - I have also reproduced this condition on a 2nd computer running Windows 7, using the same Wells Fargo link and Firefox v107

Hi David, thank you for recording the video, now I can reproduce the issue! (I was testing on a different sign-in form of the website).

Comment 11

[Dimi Lee [:dimi]]

Attachment: Screenshot 2022-11-22 at 13.41.43.png

It seems after we can username.setUserInput (or password.setUserInput) here, an error occurs. I guess the error might be the reason why username/password are not filled.

Note, Test with both Chrome and Safari, they don't have this issue.

Comment 12

[jeremy.leland]

I think this bug may be preventing me from signing into Wells Fargo website. When I try signing in on my default profile (which has saved user/password for Wells Fargo), I get message "That combination doesn't match our records." When I open console, I see an error similar to the above:

ERROR can't access property "merge", r.current is undefined TypeError: can't access property "merge", r.current is undefined
m https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/0.2d945b14e107c71513b9.chunk.js:1
    handleChange https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/0.2d945b14e107c71513b9.chunk.js:1
    u https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    p https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    b https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    b https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    ut https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    forEach self-hosted:203
    it https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    ct https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    ht https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    D https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    q https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    Zt https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    Xt https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    unstable_runWithPriority https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    Ko https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    M https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    Yt https://connect.secure.wellsfargo.com/auth/static/ui/loginaltsignon/public/js/vendor.0f3b274789da9fa3a8b1.chunk.js:2
    _fillForm resource://gre/modules/LoginManagerChild.sys.mjs:3109
    loginsFound resource://gre/modules/LoginManagerChild.sys.mjs:2156

When I create a new Firefox profile (without any saved passwords), I am able to log in with the same credentials without issue.

Should this issue be higher severity/priority, since it appears to prevent using a major banking website?

Comment 13

[jeremy.leland]

To clarify, the error in console seems to only happen when I log in from: https://connect.secure.wellsfargo.com/auth/login/present. When I try to log in directly from https://www.wellsfargo.com/ (on left side of maximized page), I don't see the error in console.

In both cases, I still get the "That combination doesn't match our records" response when using Default Profile (with password). In both cases, I am able to login successfully if I switch to a new profile that does not have any passwords saved.

Comment 14

[jeremy.leland]

I just tried again this morning. It worked on a New Profile after saving credentials. But then it also worked on my main profile (I wasn't using the saved credentials before, I was manually typing in the correct password.)

I'd swear up and down I did this multiple times on multiple computers the other night. Not sure if Wells Fargo changed something on their end, or if I somehow wasn't doing what I thought I was doing.

Either way, I am able to login now, so I'm taking back my comments about this breaking a banking website. (I still get the errors in console, but it does not appear to prevent login at this point.)