You click into a form, your browser offers your saved address, you accept it, and then half the fields stay empty. Or the browser offers nothing at all. This is one of the most common frustrations with online forms, and it is rarely your fault. Built-in autofill depends on how each website is built, and many modern sites are built in ways it cannot read.
Quick fixes to try first
- Check that autofill is on. In Chrome, open Settings, then Autofill and passwords, then Addresses and more, and make sure saving and filling addresses is enabled. In Edge, open Settings, then Profiles, then Personal info.
- Check your saved data. An old address or a missing phone number means there is nothing to fill. Edit the saved entry and try again.
- Start in the first field of the section. Browsers usually offer suggestions when you focus a name or address field, then fill the related fields together.
- Reload the page. Some forms load their fields after the page appears, and the browser only scans what was there at the start.
- Turn off other extensions temporarily. Two extensions fighting over the same field can stop either from working.
- Update your browser. Autofill improvements arrive regularly.
The technical reasons autofill fails
If the quick fixes do not help, the form itself is probably the cause. These are the usual culprits.
- Missing autocomplete attributes. Browsers recognise fields mainly by standard names such as given-name, email, or postal-code. When developers leave them out, the browser has to guess, and often guesses nothing.
- autocomplete="off". Some sites ask browsers not to fill fields at all. Browsers ignore this for some field types but respect it for many others.
- Custom dropdowns. Many sites draw their own dropdowns and radio buttons instead of using standard form elements. Browser autofill only understands the standard ones.
- Shadow DOM components. Modern web components can hide their inputs inside a "shadow root" that ordinary page scripts and autofill do not see.
- Embedded frames (iframes). Application portals often load the form from another domain inside a frame. Autofill and many tools treat each frame separately.
- JavaScript frameworks. Sites built with React, Vue, or Angular track input values in their own state. If a value is inserted without the events the framework listens for, the field looks filled but the site still thinks it is empty and shows a validation error.
- Custom questions. Autofill only knows your contact and payment details. "Years of experience with SQL" or "Are you willing to relocate?" are simply outside what it stores.
What to do when built-in autofill is not enough
If you regularly hit these problems on long forms, a dedicated form-filler extension is designed for exactly these cases. Look for one that reads field labels rather than only autocomplete names, handles custom dropdowns, reaches into Shadow DOM and iframes, and fires the input, change, and blur events modern frameworks need.
Aullevo was built around these problems: it detects text fields, native and custom dropdowns, radio buttons, checkboxes, date pickers, and file inputs; reaches inputs inside open and closed Shadow DOM components and every frame on the page; and sets values through native input setters so React, Vue, and Angular apps register every answer. A Highlight mode shows which fields it detected before you fill.
Tip: If a filled field shows an error the moment you click Next, the site probably did not register the value. Click into the field, type a space and delete it, and the framework will usually pick up the value.
When nothing fills the form
A small number of forms are deliberately hard to automate, such as banking and identity verification pages, or fields that block pasting. Treat those as a signal to slow down and type carefully. They are usually the places where a mistake matters most.