form-filling（表格填写）

Form Filling — Detect, Fill, Submit, Verify

Works on login forms, contact forms, registration, checkout, search, multi-step wizards. Read chrome-bridge first.

Workflow

1. Discover — enumerate fields
2. Build selector strategy — pick the most stable handle per field
3. Fill — dom_fill for plain inputs, dom_type for rich editors, execute_script for everything else
4. Verify — read back the values before submitting
5. Submit — click the submit button (or fallback to form.submit())
6. Confirm — check URL change or success message after submit

Reusable scripts

Each capability has a focused JS file under scripts/. To use one:

1. Read the script file to load it as a string.
2. Pass the contents as the code argument to mcp__chrome-bridge__execute_script.
3. Many scripts have selector / value placeholders embedded — edit before passing.

Step 1: Discover fields

execute_script(code=<contents of scripts/discover_fields.js>)

Step 2: Pick selectors

Priority order when choosing a handle per field:

1. #id — most reliable if the field has an id
2. [name="fieldname"] — reliable for named fields
3. [type="email"], [type="tel"], [type="password"] — reliable for typed inputs when the form has one per type
4. [placeholder="..."] — fallback for unnamed fields
5. [aria-label="..."] — accessible forms
6. Positional (form:nth-of-type(1) input:nth-of-type(2)) — last resort

Step 3: Fill

Plain inputs, textareas, selects

dom_fill('#email', 'user@example.com')
dom_fill('[name="password"]', 'hunter2')
dom_fill('textarea[name="message"]', 'Hello...')
dom_fill('select[name="country"]', 'MY')   # matches by value

Rich text editors (ProseMirror, TipTap, Draft.js, contentEditable)

dom_type('[role="textbox"][aria-label*="comment" i]', 'Thanks for sharing!')

dom_fill silently fails on these editors. They listen to real keystroke events, not .value assignment or input events. dom_type simulates actual CDP Input.dispatchKeyEvent — it's the only thing that works on LinkedIn, Threads, Notion, Slack, and most comment boxes on modern sites.

Radio buttons

# Edit name+value in scripts/radio_set.js, then:
execute_script(code=<contents of scripts/radio_set.js>)

Checkboxes

# Edit name in scripts/checkbox_set.js, then:
execute_script(code=<contents of scripts/checkbox_set.js>)

Date pickers (native <input type="date">)

# Edit value in scripts/date_input_set.js, then:
execute_script(code=<contents of scripts/date_input_set.js>)

Autocomplete fields

# Type character-by-character to trigger the suggestion list:
dom_type('input[name="location"]', 'Kuala Lumpur')
# Wait 1-2s for suggestions, then click the one you want:
dom_click('[role="option"]:first-child')

Step 4: Verify before submit

execute_script(code=<contents of scripts/form_values_dump.js>)

Step 5: Submit

dom_click('button[type="submit"]')

If there's no submit button or click does nothing:

execute_script(code="(function(){ document.forms[0].submit(); return 'submitted'; })()")

Step 6: Confirm

# wait 3s for the response
execute_script(code="(()=>location.href)()")  # did we redirect to a success page?
page_text()                                    # is there a "Thank you" / "Success" / error message?

React/Vue framework edge case

If dom_fill appears to work (value is set) but form validation still fails or the submit button stays disabled, the framework state didn't update. Use the native setter pattern:

# Edit selector + value in scripts/native_setter_input.js, then:
execute_script(code=<contents of scripts/native_setter_input.js>)

Multi-step wizards

# 1. Detect current step
execute_script(code="(function(){ return document.querySelector('.wizard-step.active')?.dataset.step || '?'; })()")
# 2. Fill this step's fields (discover → fill → verify)
# 3. Click Next
dom_click('button.next')   # or use execute_script to match by innerText if class varies
# 4. Wait for the next step to render, then repeat until you hit the final submit

CAPTCHA handling

execute_script(code=<contents of scripts/captcha_detect.js>)

If present, stop and tell the user to solve it manually. Never try to solve CAPTCHAs programmatically.

Common failures