FA-22429 / Autocomplete interactions / Member archive
Unavailable suggestion presentation: no selectable option is confused with no returned option · case 04
The status completion transition produces an incorrect observable state.
Case contract
Unavailable options remain visible with reasons but cannot be committed or auto-selected. Availability is attached to identity, not display text. A committed unavailable value remains represented for correction. Disabled-only responses are distinct from empty results.
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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| normal status | "unavailable" | "available" | 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.
Sign in to the archive ↗