Skip to content

Conversation

@n0mer
Copy link

@n0mer n0mer commented Nov 13, 2025

The sign-up form is missing autoComplete attributes on several input fields, which causes browser warnings about missing autocomplete attributes.

This PR adds:

  • autoComplete="name" - name input field
  • autoComplete="username" - username input field
  • autoComplete="email" - email input field
  • autoComplete={field} - additional field number input
  • autoComplete={field} - additional field text input

Note: Password inputs already have autoComplete="new-password" set correctly.

The sign-in form already has proper autocomplete attributes, so this PR brings the sign-up form to the same standard.

This addresses browser accessibility warnings and improves form usability with password managers and autofill features.

@n0mer n0mer force-pushed the fix/add-autocomplete-to-signup-form branch 2 times, most recently from 7bfc0d6 to b648266 Compare November 13, 2025 04:36
The sign-up form is missing autoComplete attributes on several input fields, which causes browser warnings about missing autocomplete attributes.

This PR adds:
- autoComplete="name" to the name input field
- autoComplete="username" to the username input field
- autoComplete="email" to the email input field
- autoComplete={field} to additional field inputs (number and text types)

Note: Password inputs already have autoComplete="new-password" set correctly.

The sign-in form already has proper autocomplete attributes, so this PR brings the sign-up form to the same standard.

This addresses browser accessibility warnings and improves form usability with password managers and autofill features.
@n0mer n0mer force-pushed the fix/add-autocomplete-to-signup-form branch from b648266 to 52c1a5a Compare November 13, 2025 04:37
"number" ? (
<Input

autoComplete={field}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we can put dynamic fields into autoComplete here since they could be invalid options for this prop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants