Open Bug 1584944 Opened 6 years ago Updated 3 years ago

The password and/or username is not being auto-filled on alipay.com

Categories

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

Desktop
All
defect

Tracking

()

Tracking Status
firefox69 --- affected
firefox70 --- affected
firefox71 --- affected
firefox72 --- affected
firefox73 --- affected
firefox74 --- affected
firefox75 --- affected

People

(Reporter: danibodea, Unassigned)

References

()

Details

Attachments

(1 file)

Note

  • The password manager does not auto-fill the password and/or username on alipay.com.

Affected versions

  • Nightly v71.0a1
  • Beta v70.0b10

Affected platforms

  • all

Steps to reproduce

  1. Reach https://auth.alipay.com/login/index.htm?goto=https%3A%2F%2Fwww.alipay.com%2F
  2. Input some random credentials and tap ENTER.
  3. When the password manager saved drop-down appears, input the uncaptured username and save it.
  4. Clear the cash and re-open the login page.

Expected result

  • The username and password are being auto-filled.

Actual result

  • The username and password are NOT being auto-filled.

Additional notes

  • If the cash is not cleared in step 4, the username will be auto-completed (by cache).
  • The context menu over the password manager is disabled or does not work.
Summary: The password and/or username in not being autofilled on alipay.com → The password and/or username is not being autofilled on alipay.com
Summary: The password and/or username is not being autofilled on alipay.com → The password and/or username is not being auto-filled on alipay.com

Can you enable debug logging with these STR and attach the output here? We log out details on why a form is being or not being autofilled so that should help diagnose.

Flags: needinfo?(daniel.bodea)

The logs displayed while performing step 4:

TypeError: this.document is undefined
2 UrlbarInput.jsm:935:5
webrtc.peerconnection.datachannel_created - Unknown scalar.
LoginManagerContent: onDOMFormHasPassword, visibilityState: visible isMasterPasswordSet: false LoginManagerContent.jsm:684:8
LoginFormFactory: adding <unavailable> to root elements for <unavailable> LoginFormFactory.jsm:68:9
LoginManagerContent: _processDOMFormHasPasswordEvent: <unavailable> <unavailable> LoginManagerContent.jsm:703:8
LoginManagerContent: _detectInsecureFormLikes https://auth.alipay.com/login/index.htm?goto=https%3A%2F%2Fwww.alipay.com%2F LoginManagerContent.jsm:870:8
LoginManager: searchLogins: formActionOrigin or httpRealm is recommended LoginManager.jsm:472:13
LoginFormFactory: adding <unavailable> to root elements for <unavailable> 3 LoginFormFactory.jsm:68:9
LoginRecipes: cacheRecipes: for: https://auth.alipay.com LoginRecipes.jsm:233:9
LoginManagerContent: _fillForm <unavailable> LoginManagerContent.jsm:1755:8
LoginRecipes: _filterRecipesForForm <unavailable> LoginRecipes.jsm:285:9
LoginRecipes: getFieldOverrides: filtered recipes: <unavailable> LoginRecipes.jsm:313:9
LoginManagerContent: Username field <unavailable> has name/value/autocomplete: / / LoginManagerContent.jsm:1270:10
LoginManagerContent: Password field <unavailable> has name: LoginManagerContent.jsm:1286:10
LoginManagerContent: _stopTreatingAsGeneratedPasswordField LoginManagerContent.jsm:1573:8
LoginManagerContent: Saving autoFilledLogin {73227437-6611-42c7-b40a-54efbeff8665} for <unavailable> LoginManagerContent.jsm:2068:12
LoginManagerContent: _fillForm succeeded LoginManagerContent.jsm:2082:10
LoginManagerContent: _fillForm: Attaching event listeners to usernameField LoginManagerContent.jsm:2118:12
LoginManagerContent: onDOMFormHasPassword, visibilityState: visible isMasterPasswordSet: false LoginManagerContent.jsm:684:8
LoginFormFactory: adding <unavailable> to root elements for <unavailable> LoginFormFactory.jsm:68:9
LoginManagerContent: _processDOMFormHasPasswordEvent: <unavailable> <unavailable> LoginManagerContent.jsm:703:8
LoginManagerContent: _detectInsecureFormLikes https://auth.alipay.com/login/index.htm?goto=https%3A%2F%2Fwww.alipay.com%2F LoginManagerContent.jsm:870:8
LoginManager: searchLogins: formActionOrigin or httpRealm is recommended LoginManager.jsm:472:13
LoginFormFactory: adding <unavailable> to root elements for <unavailable> 2 LoginFormFactory.jsm:68:9
LoginRecipes: cacheRecipes: for: https://auth.alipay.com LoginRecipes.jsm:233:9
LoginManagerContent: _fillForm <unavailable> LoginManagerContent.jsm:1755:8
LoginRecipes: _filterRecipesForForm <unavailable> LoginRecipes.jsm:285:9
LoginRecipes: getFieldOverrides: filtered recipes: <unavailable> LoginRecipes.jsm:313:9
LoginManagerContent: Username field <unavailable> has name/value/autocomplete: / manualyinputusername / LoginManagerContent.jsm:1270:10
LoginManagerContent: Password field <unavailable> has name: LoginManagerContent.jsm:1286:10
LoginManagerContent: form not filled, the password field was already filled LoginManagerContent.jsm:1945:12
LoginManagerContent: _fillForm: Attaching event listeners to usernameField LoginManagerContent.jsm:2118:12
LoginManagerContent: _detectInsecureFormLikes https://auth.alipay.com/login/index.htm?goto=https%3A%2F%2Fwww.alipay.com%2F LoginManagerContent.jsm:870:8
LoginFormFactory: adding <unavailable> to root elements for <unavailable> LoginFormFactory.jsm:68:9
LoginAutoCompleteResult: AutoCompleteSearch invoked. Search is: LoginAutoCompleteResult.jsm:484:9
LoginFormFactory: adding <unavailable> to root elements for <unavailable> LoginFormFactory.jsm:68:9
LoginManager: searchLogins: formActionOrigin or httpRealm is recommended

Is this what you need?

Flags: needinfo?(daniel.bodea)

The logs show that the password field is being filled. I wonder if we are finding a different - perhaps hidden - password field.
When you say you clear [cache], which cache specifically are you clearing - and why?

I'm not sure how to get to the login form on alipay - when I load the URL in Step 1 comment #0, I just get a page with a QR code on it?

Flags: needinfo?(daniel.bodea)

The cache I clear in step 4 is in about:preferences, Privacy & Security tab, Cookies and Site Data section, "Clear Data..." button (both options checked).
The reason I clear it is because on some sites, credentials get auto-filled from the cache and I want to make sure that I can simulate a clean new session. On this site, after attempting to log in (with an invalid account) to save a set of credentials, the username remains in the field, so instead of just reopening the page, I also clear the cache. Is it a bad practice?

Flags: needinfo?(daniel.bodea)

I have made this attachment with instructions on how to get to the login form.

Priority: -- → P3

Updating affected flags

Depends on: 1790970
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: