FAILURE MAP
← Case archive

FA-32068 / Keyboard interactions / Member archive

Composition replacement against document revisions: Stale composition replacement overwrites a newer document revision · case 03

The event trace violates the conflict compare rule and produces incorrect keyboard state or command output.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Case [document,revision,events]. Events [kind,a,b,text]. Begin captures valid range [a,b) and current revision with preedit text; update replaces pending preedit; external replaces entire document and increments revision. Commit applies pending replacement only if captured revision still equals current, otherwise counts stale conflict; either path closes pending. Cancel discards pending. Return document, revision, pending [lo,hi,base,text] or None, conflicts. 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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
composition-revision scenario 3[["nX", 6, null, 0], ["nX", 6, null, 0], ["nX", 6, null, 0]][["new", 5, null, 1], ["new", 5, null, 1], ["new", 5, null, 1]]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 ↗