FA-22787 / Autocomplete interactions / Member archive

Autocomplete form binding: form reset keeps an uncommitted completion fragment · case 02

The reset-draft completion transition produces an incorrect observable state.

Member previewVariant 2 · 3 implementations · 22 checks per implementation

Case contract

Form submission serializes committed suggestion identifiers separately from visible draft text. Required checks apply to committed values, an empty-string identifier is present, disabled fields are omitted, and reset restores the initial identity and label together. Multi-value fields preserve separate values.

Why this case matters

Autocomplete couples draft text, suggestion identity and asynchronous presentation; this bounded lifecycle model isolates one observable interaction defect.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
normal reset-draft	`{"active": null, "draft": "peach"}`	`{"active": null, "draft": "Plum"}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.