Not through Puppeteer’s documented ElementHandle.autofill() method, according to the current Puppeteer 25.12.0 API reference: it documents credit-card autofill only, in Chrome’s new headless and headful modes. AutofillAddressField is a vocabulary of supported address-field names, not proof that this method can fill an address. Chromium separately exposes experimental address autofill through its DevTools Protocol.
What does AutofillAddressField mean?
The Puppeteer API index describes AutofillAddressField as “Supported autofill address field names.” It identifies names for address data; it is not itself a method, a guarantee of runtime support, or evidence that an address form can be filled by ElementHandle.autofill(). See the Puppeteer API index.
As an Amazon Associate I earn from qualifying purchases.
This distinction matters when reading types or autocomplete examples: a field-name enum can exist before, or independently of, a high-level API that accepts and fills address data.
What does Puppeteer’s documented autofill method support?
The current ElementHandle.autofill() reference describes a method called on an input element handle. It accepts AutofillData, returns a promise, and throws if the form cannot be autofilled. Its remarks limit documented support to credit-card information in Chrome’s new headless and headful modes. The page identifies its documentation version as Puppeteer 25.12.0.
#1 Best Overall
Therefore, do not infer address autofill from the presence of AutofillAddressField, or assume an address payload passed to autofill() is supported. Verify the documentation for the exact Puppeteer version and browser mode you have installed before relying on this method.
What are the address autofill options?
| Option | Address support described | Best suited to | Scope and caveat |
|---|---|---|---|
Puppeteer ElementHandle.autofill() |
Current reference documents credit-card information, not addresses. | Using Puppeteer’s documented autofill abstraction for card data. | Current reference is for Puppeteer 25.12.0 and specifies Chrome new headless and headful modes. Confirm the installed version’s documentation. |
Chromium DevTools Protocol Autofill domain |
Defines an address trigger command and test-address setup. |
Protocol-level address autofill automation or investigation. | Experimental Chromium protocol functionality; not evidence of address support in Puppeteer’s high-level method. |
| Chrome DevTools Autofill panel | Inspects address field detection, predicted values, and inserted values; supports test address data. | Interactive diagnosis of how Chrome recognizes a form. | A visual debugging panel, not an automated Puppeteer API. |
How does Chromium’s protocol-level address autofill work?
The Chromium DevTools Protocol Autofill definition marks its Autofill domain experimental. Its Autofill.trigger command identifies an anchor form field and accepts either address data or credit-card data; the two kinds of input are mutually exclusive. The protocol says the submitted address or card data is not saved.
Address data and results
Protocol address data is an array of fields, each with a name and value. The addressFormFilled event reports the fields filled and a UI representation of the address. Its FilledField information includes the HTML type, ID, name, value, inferred autofill type, filling strategy, frame ID, and backend node ID.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThe protocol distinguishes fields filled through an HTML autocomplete attribute from those filled through autofill heuristics. A form’s semantic markup and whether Chrome recognizes its fields can therefore affect what gets filled.
Test addresses
The protocol’s Autofill.setAddresses command supplies test addresses for verifying form implementations. This is a separate, experimental protocol route. It should not be presented as a stable, documented Puppeteer address-autofill method.
How can you inspect an address form in Chrome DevTools?
For interactive diagnosis, Chrome’s Autofill panel maps detected page fields to predicted address values and shows values Chrome inserted. The Chrome DevTools Autofill guide says the panel inspects address information and supports test address data, so you can examine form recognition without using personal address details. The guide was last updated April 16, 2024; menu labels and interface details can change.
Rank #3
- Open the page and its form in Chrome DevTools.
- Open the Autofill panel and review which fields Chrome detected and the values it predicts.
- Use the panel’s test address data, focus a form field, and choose a test option to observe the inserted values.
- Compare the detected fields with the form’s labels and
autocompleteattributes when a field is missing or misidentified.
Chrome also has an “Addresses and more” setting for enabling “Save and fill addresses,” and can save addresses entered into forms. For repeatable development tests, use test address data where possible rather than personal details.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How should you choose a Puppeteer/browser route?
- Need documented high-level Puppeteer autofill? Use
ElementHandle.autofill()only for the credit-card behavior described by the version-specific reference, and in the stated Chrome modes. - Need address filling in automation? Chromium’s protocol defines an experimental address route. Treat it as protocol-level work, verify compatibility with your actual Puppeteer and browser versions, and account for its experimental status.
- Need to find why Chrome misses a field? Use the DevTools Autofill panel to inspect predictions and inserted values, ideally with its test address data.
Puppeteer uses Chrome DevTools Protocol by default to automate Chrome and WebDriver BiDi by default for Firefox; it also supports BiDi for Chrome. Its releases are tightly bundled with specific browser releases to maintain protocol compatibility. Check the Puppeteer FAQ and verify the exact installed Puppeteer/browser pair before depending on protocol behavior.
What commonly goes wrong?
The enum exists, but address autofill does not work
Cause: The enum only names address fields; the current high-level autofill() documentation describes card data only. Fix: Do not treat the enum as a supported address-filling call. Use the experimental protocol route if it fits your needs, or inspect field recognition in DevTools.
autofill() throws or the form remains unchanged
Cause: The method can throw when a form cannot be autofilled, and its documented scope is limited to card information in Chrome new headless and headful modes. Fix: Confirm that the requested data and runtime match the installed version’s documentation; do not use it as an address-fill workaround.
Chrome detects some fields but not others
Cause: Autofill can use an autocomplete attribute or browser heuristics, and the protocol exposes which strategy was used. Fix: Inspect predictions and inserted values in the Autofill panel, then check the form’s semantics and field markup.
Protocol behavior differs after an upgrade
Cause: The Autofill domain is experimental, and Puppeteer versions are paired with specific browser releases for protocol compatibility. Fix: Re-check the protocol schema and the installed Puppeteer/browser versions rather than assuming a previous experimental setup remains compatible.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your goal is to capture the form’s rendered appearance rather than populate its fields, ScreenshotNeo returns a website screenshot or PDF with one GET request. It is not an address-autofill tool.
For the address form page, using the API’s documented call pattern:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/address-form -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, newsletter popups, and chat widgets are removed before the shot; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. An MCP server offers take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Sign up for 1,000 free screenshots a month, no card required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
