Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`<SignIn />` and `<SignUp />` email and name fields have no `autocomplete`, so browsers don't offer the user's email

Aberta
  • Algo errado?
#10,285 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
72/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
next.js, react, typescript
Domínio
accessibility, authentication, frontend

Direção de pesquisa

Start with packages/ui/src/components/SignIn/SignInStart.tsx at the identifier field mentioned in the issue, then locate the corresponding SignUp fields and their tests. Check how identifier types and passkey autofill are handled, and run the relevant component tests. Done when the fields receive the standard autocomplete tokens described in the issue, including a valid field name before webauthn.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Reproduction

No special setup needed: any app with the default <SignIn /> / <SignUp /> and email (email code) as the only identifier shows it, e.g. a fresh Next.js quickstart.

Description

With email as the sign-in identifier, the prebuilt components render the email and name fields without any autocomplete attribute:

<!-- <SignIn /> -->
<input id="identifier-field" name="identifier" type="text" inputmode="email" ...>

<!-- <SignUp /> -->
<input id="firstName-field" name="firstName" type="text" ...>
<input id="lastName-field" name="lastName" type="text" ...>
<input id="emailAddress-field" name="emailAddress" type="text" inputmode="email" ...>

So Safari (macOS/iOS/iPadOS), the iOS QuickType keyboard and password managers can't tell the field is an email field, and they don't offer the user's email. This is worst with passwordless sign-in (email code): there's no password field, so the browser never saves a login. Users type their full email by hand on every sign-in. We see it in session recordings: the same users typing their email letter by letter every week, and users have reported it.

type="text", name="identifier" and a translated label (here French, "Adresse e-mail") leave the browser almost nothing to guess from.

In the source, the identifier field only gets autocomplete when passkey autofill is on, and then the value is webauthn on its own:

https://github.com/clerk/javascript/blob/485eba446a6fdc3a821f2d970059408e0bada741/packages/ui/src/components/SignIn/SignInStart.tsx#L676

autoComplete={isWebAuthnAutofillSupported ? 'webauthn' : undefined}

There's no prop or appearance option to set it, so the only workaround is adding the attribute to Clerk's DOM from outside with a MutationObserver.

Steps to reproduce:

  1. Enable email (email code) as the only identifier in the dashboard.
  2. Render <SignIn /> (or <SignUp />).
  3. Inspect the email field, or focus it in Safari on iOS/iPadOS.

Expected behavior:

The fields carry standard autocomplete tokens, so browsers, keyboards and password managers can offer the user's details:

  • Sign-in identifier: email when email is the only identifier, tel for phone only, username for username or mixed identifiers. With passkey autofill, add webauthn after the field name (username webauthn, email webauthn). A bare webauthn isn't a valid value per the HTML spec, which expects it after a field name.
  • Sign-up: email on emailAddress, given-name on firstName, family-name on lastName, tel on phoneNumber, username on username.

This is also an accessibility issue: WCAG 2.1 SC 1.3.5 Identify Input Purpose (Level AA) asks for autocomplete on fields that collect the user's own information.

Actual behavior:

No autocomplete attribute on these fields (unless passkeys are on, then a bare webauthn). Safari and the iOS keyboard don't suggest the user's email.

Environment
@clerk/nextjs: 7.5.2
@clerk/clerk-js: 6 (loaded from Frontend API)
@clerk/ui: 1.40.0 (loaded from Frontend API)
next: 16.3.1
react: 19
Seen in: Safari on iPadOS (user report); confirmed in Chromium and WebKit (Playwright)
Linguagem predominante
TypeScript
Estrelas
1.8k
Forks
480
Merge médio
1d 19h
PRs com merge (30d)
285

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de clerk/javascript

Todas as issues de clerk/javascript

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.