Closed Bug 1820830 Opened 2 years ago Closed 1 year ago

Password autocomplete not working for gmail in private browsing

Categories

(Firefox for Android :: Autofill, defect)

Firefox 111
All
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jf.dev, Unassigned)

Details

(Whiteboard: [qa-triaged])

Steps to reproduce:

In private browsing, open https://mail.google.com et try to use the password autocomplete feature to login to your account. Login information for gmail is saved in Firefox password manager.

Actual results:

In the saved identifiants section, the login informations is proposed but, when I click on it, the password autocomplete feature doesn't input the mail address.

Expected results:

In the saved identifiants section, the login informations is proposed and, when I click on it, the password autocomplete feature inputs the mail address. Then the password can be inputted by the password autocomplete feature

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Flags: needinfo?(cpeterson)
Severity: -- → S3
Component: General → Autofill
Flags: qe-verify+

Thank you for the report, Jerome!

I was not able to reproduce this issue on the latest Firefox for Android 121.1.0 build, nor on Nightly 123.0a1 from 1/12, using a Google Pixel 6 (Android 14), and a Lenovo tablet M10 (Android 10).

Could you, please, retry on the latest versions of Firefox for Android and, if you still reproduce this, provide us some more details:

  • the device you encountered this issue on,
  • the version of the Firefox for Android,
  • if you have any add-ons enabled, or some settings changed.
Flags: qe-verify+ → needinfo?(jf.dev)
Whiteboard: [qa-triaged]

Hello !
I tried to reproduce just now and the issue seems fixed. It can be closed. Thank you !

Flags: needinfo?(jf.dev)

Closing as WORKSFORME, thank you!

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.