FA-23278 / Autocomplete interactions / Member archive

Unresolved autocomplete draft on blur: strict-selection blur treats unresolved text as a new free-text option · case 03

The free-text-rejection completion transition produces an incorrect observable state.

Member previewVariant 3 · 3 implementations · 22 checks per implementation

Case contract

This strict-selection picker reverts an unresolved draft to the committed label after blur unless a suggestion pointer acceptance or IME composition is in progress. Exact unique candidate confirmation is an explicit separate transition. Blur never chooses a highlighted candidate merely because it exists.

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 free-text-rejection	`{"free_text": "peach", "resolved": true}`	`{"free_text": null, "resolved": true}`	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.