Guidance for disabling browser autofill in data-entry forms

[shreyam1008]

I’m using TanStack Form for an internal data-entry app. One operator enters records for many different people on the same browser. Chrome and Safari may suggest the operator’s saved address, password managers attach to password fields, and normal inputs offer values from previous records. That makes it easy to put one person’s data into another record.

Today I add autocomplete="off" to the form and individual inputs:

<form autoComplete="off">
  <form.Field name="address.line1">
    {(field) => (
      <input
        name={field.name}
        autoComplete="off"
        value={field.state.value}
        onChange={(e) => field.handleChange(e.target.value)}
      />
    )}
  </form.Field>
</form>

This is inconsistent across browsers and password managers, and easy to miss in reusable field components.

Since TanStack Form is headless, I’m not expecting it to override browser behavior. Could the docs include a recommended best-effort pattern for this use case, covering address, password, and ordinary text fields, plus the limits that cannot be controlled? A small example using shared field components would be enough.