1900009 - Saved Email address for ChatGPT Login not automatically filled in

Status: RESOLVED FIXED

(Toolkit :: Password Manager, defect, P3)

Description

[loeper]

Steps to reproduce:

1. create a login for ChatGPT with email address and password (if not existing)
2. turn on credentials saving and login to ChatGPT, save credentials
3. goto https://chatgpt.com/auth/login
4. click on "Log in"

Actual results:

1. A new page appears with a field "Email address". The field ist empty.
2. Clicking into the field brings no reaction.

Expected results:

1. The field should contain the email address from the saved credentials or a list of fitting credentials to choose
2. If 1. is not possible, a click into the field should give a list of saved credentials to choose. Clicking one of the list items should fill in the choosen email address.

Comment 1

[loeper]

Attachment: in Chrome, after clicking the field a list (menu) with email addesses from saved credentials appears

Comment 2

[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 3

[Issam Mani [:issammani]]

Hey loeper, Thanks for reporting. I can confirm this is happening on latest release.
After doing some digging, the initial page has a formless username input of this shape:

<input class="email-input " inputmode="email" type="email" id="email-input" name="email" autocomplete="username" autocapitalize="none" spellcheck="false" required="" placeholder="">

We don't show the autofill popup on username inputs without a form right now.

I think this is something we can add. Right now, we only dispatch DOMFormHasPossibleUsername for text and email inputs within a form. I think we can allow autocomplete="username without a form too since this is a strong hint that a field is a username.

Alternatively, we can also check here if autocomplete="username and add LoginManager as a provider for that input.

Dimi what do you think ?

Comment 4

[Dimi Lee [:dimi]]

Yes, i agree supporting formless username-only form when the input has autocomplete="username" is a good start.
Besides supporting formless username-only form, we also need to check whether we can recognize this <input> as a "
login" form (see the code block here).

Comment 5

[Ryan Safaeian [:rsafaeian]]

Attachment: WIP: Bug 1900009 - Dispatch DOMFormHasPossibleUsername event for formless inputs with autocomplete="username".

Comment 6

[Ryan Safaeian [:rsafaeian]]

Attachment: Bug 1900009 - Dispatch DOMPossibleUsernameInputAdded event for valid text and email inputs. r=dimi!

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6a254993ba42
Dispatch DOMPossibleUsernameInputAdded event for valid text and email inputs. r=dimi,edgar

Comment 8

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/6a254993ba42