Autofill Forms by RuleChrome autofill not filling a field? Why it happens and what to do
Chrome's built-in autofill is good at standard fields: name, address, e-mail, phone, card. It often skips everything else. These are the usual reasons.
1. The field isn't a standard type
Chrome fills fields it can recognise, mostly from the page's autocomplete hints and the field's name and
label. A field like "Customer reference", "Project code" or "Reason for visit" has no standard meaning, so Chrome has
nothing to put there.
2. The site uses custom input components
Many modern sites (React, Angular and similar) draw their own inputs. Even when a value is placed in the box, the page may not "notice" it unless it receives the input events it listens for, so the value disappears or the form says the field is empty.
3. The form is inside a frame
Payment forms and embedded widgets often live in an iframe from another site. Autofill treats each frame separately, so some fields fill and others don't.
4. The field names change on every visit
Some systems generate field IDs like input_8f3a2c that are different every time. Anything that remembers
fields by their exact name will miss them on the next visit.
What you can do
- Check Settings > Autofill and passwords: make sure addresses are saved and the toggle is on.
- For your own non-standard fields, use a tool that fills by your own rules: "on this site, put this value in the field whose label or name matches this".
- For changing names, match with a pattern (a regular expression) instead of the exact ID.
- Never store passwords or card numbers in a general form filler; use your password manager for those.