Skip to main content

Demo · Advanced

Controls beyond plain inputs

01

Works automatically

Plain div elements and buttons with ARIA roles - the way Radix, MUI, and Headless UI render them - plus editors that only accept text through their own document model. No setup needed.

Custom widgets

A combobox, a date picker, a switch, and a radio group. No native inputs involved.

Favorite fruit
Delivery date
Newsletter
T-shirt size

Rich text & editors

Plain and plaintext-only editable hosts, a model-backed editor, and a real Tiptap editor.

Notes (contenteditable)
Comment (plaintext-only)
Bio (model-backed editor)

Editor model: (empty)

Bio (Tiptap)
Tiptap / ProseMirror
Editor model: (empty)

02

Taught with Recipes

Some controls give no clue they are controls, or only react to a hover. A Recipe teaches FillMatic once: match the control with a CSS selector, then replay a few steps. These three ship built in. How Recipes work

Unlabeled dropdown

Plain div elements with no roles or labels - nothing marks it as a control.

Choose a flavor…

Recipe for #w-legacy-fruit

  1. Click @self
  2. Click random .legacy-option

Waiting for Fill all fields

Hover-only menu

Clicking does nothing - the menu opens on hover. Steps reach it through the control's own wrapper, so several pickers never mix up options.

Assign to

Recipe for #w-assignee

  1. Hover @self
  2. Wait for @closest(.hover-picker) .hover-item
  3. Click random @closest(.hover-picker) .hover-item

Waiting for Fill all fields

Material UI Autocomplete

A real library control. The Recipe opens it and picks from the rendered listbox.

No framework selected yet

Recipe for input[role="combobox"]

  1. Click @self
  2. Click random [role="option"]

Runs on every site, so it covers MUI Autocompletes anywhere.

NextHow Recipes workTeach FillMatic any control with a selector and a few steps.