form_input
Populate textboxes, checkboxes, dropdowns, and other form controls in a Firefox page via a ref from read_page, triggering native input/change events for React compatibility.
Instructions
Fill one form control that read_page has already tagged with a ref, without aiming a click at it. ref, value and tabId are all required. Text boxes, textareas, number and date fields, contenteditable regions, checkboxes, radios and dropdowns are covered; a file input is not, and goes through file_upload or upload_image, which read only from the directories this server is allowed to open. The write goes through the element's native setter and is followed by input and change events, while checkboxes and radios are toggled with a real click, so React and its relatives notice the change. A dropdown is matched against option values first, then against the labels shown to the user, ignoring case on a last pass; when nothing matches, the error lists the options that exist. Disabled controls are turned down. A ref lives only as long as the node behind it, so after a navigation, a reload, or a re-render that swaps the element out, run read_page again or this fails with an unknown-ref error.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | Yes | The element id read_page handed out, shaped like ref_1 or ref_2. It names one live node, so take it from the most recent read of this page; older ids are usually stale. | |
| tabId | Yes | The tab holding the element; required. Ids come from tabs_context_mcp, and the ref has to belong to that same tab's document. | |
| value | Yes | What the control should end up holding. Text-like fields take a string or a number. Checkboxes and radios take true or false (an empty string, or "false", "no", "0", "off", also reads as unchecked). A dropdown takes either the option's value attribute or the label the user sees. Arrays and objects are rejected instead of being stringified into the field. |