FAILURE MAP
← Case archive

FA-37609 / Table interactions / Member archive

Remote table page response admission: page error preserve · case 04

The table page error preserve result violates the stipulated remote table page response admission contract.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Admit remote table pages only for the exact request/query/offset. Errors retain displayed rows, duplicate row IDs retain first placement and last payload, successful totals may shrink, loading and old errors clear, and only explicit server deletions prune cross-page selection.

Why this case matters

An offline table UI model isolates remote table page response admission, including adversarial row/column relationships.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
error retains page{"error": "failed", "loading": false, "offset": 0, "query": "q", "request": 2, "rows": [], "selected": [], "total": 1}{"error": "failed", "loading": false, "offset": 0, "query": "q", "request": 2, "rows": [{"id": "old"}], "selected": [], "total": 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 ↗