FAILURE MAP
← Case archive

FA-25700 / Filter interfaces / Member archive

A new criterion edit invalidates only the branched redo history · case 05

A new criterion edit invalidates only the branched redo history is violated by the widget projection.

Member previewVariant 5 · 3 implementations · 10 checks per implementation

Case contract

Each filter edit transaction records before and after snapshots. Undo/redo moves whole constraint snapshots and does not resurrect history after a new branch edit. This example checks: A new criterion edit invalidates only the branched redo history.

Why this case matters

Filter-widget state and serialization must preserve user constraints while the view changes.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
contract fixture 0{"branch-future": [["x"], ["y"]], "noop-history": [], "redo-snapshot": ["x"], "undo-available": false, "undo-snapshot": ["a", "b"], "undo-tail": []}{"branch-future": [], "noop-history": [], "redo-snapshot": ["x"], "undo-available": false, "undo-snapshot": ["a", "b"], "undo-tail": []}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 ↗