FA-22483 / Autocomplete interactions / Member archive

Autocomplete loading and empty states: loading state gives the no-results message precedence over a failed query · case 03

The status-priority completion transition produces an incorrect observable state.

Member previewVariant 3 · 3 implementations · 22 checks per implementation

Case contract

A loading snapshot distinguishes initial loading, background refreshing, settled-empty, error and cancellation. Only settled successful empty responses show no-results. Existing rows may remain visible during refresh but are bound to the draft they represent; stale errors never overwrite a newer query status.

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 status-priority	`"loading"`	`"error"`	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.