FA-31523 / Keyboard interactions / Member archive
Explicit dead-key text composition: Completed text composition leaves a pending accent for the next character · case 03
The event trace violates the consume accent rule and produces incorrect keyboard state or command output.
Case contract
Case [mapping,events], mapping uses accent+character string keys and string replacements; events [kind,value]. Dead event sets pending accent and flushes a previous accent literally. Text with pending accent maps a pair or emits accent then character; space emits only accent. Backspace cancels pending accent, otherwise emits deletion action. Cancel clears accent; flush emits accent then clears. Return output string chunks and pending accent. Inputs are finite ordered event traces; return the stated deterministic state. Batch entries are independent. N varies the number of independent input transactions.
Why this case matters
Controlled keyboard event processing model for debugging application event logic.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| dead-key scenario 4 | [[["\u00e2", "ab"], "b", 0], [["\u00e2", "ab"], "b", 0], [["\u00e2", "ab"], "b", 0]] | [[["\u00e2", "b"], null, 0], [["\u00e2", "b"], null, 0], [["\u00e2", "b"], null, 0]] | 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 ↗