FA-31255 / Keyboard interactions / Member archive
Keyboard layout mapping generations: Mapping entries are accepted before a keyboard layout is established · case 05
The event trace violates the map lifecycle rule and produces incorrect keyboard state or command output.
Case contract
Events [kind,device,a,b]. layout replaces device generation a and clears cached labels; map caches physical code a to label b in current generation; lookup emits cached label or code a as fallback. Disconnect removes generation and cache. Maps and lookups before layout are ignored. Return emitted labels, generations and cached [device,code,label] rows. 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 |
|---|---|---|---|
| layout-cache scenario 1 | [[[], [], [["a", "KeyA", "x"]]], [[], [], [["a", "KeyA", "x"]]], [[], [], [["a", "KeyA", "x"]]], [[], [], [["a", "KeyA", "x"]]], [[], [], [["a", "KeyA", "x"]]]] | [[[], [], []], [[], [], []], [[], [], []], [[], [], []], [[], [], []]] | 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 ↗