FA-38184 / Table interactions / Member archive
Asynchronous table cell save acknowledgement: ack draft cell removal · case 04
The table ack draft cell removal result violates the stipulated asynchronous table cell save acknowledgement contract.
Case contract
A save acknowledgement belongs to an exact pending request and row, clears only that pending cell, preserves errors and newer edits, rejects older server revisions, installs canonical server values/revisions, and clears a draft only when the original edit ID still owns it.
Why this case matters
An offline table UI model isolates asynchronous table cell save acknowledgement, including adversarial row/column relationships.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| canonical server response | {"draft": [], "error": null, "pending": [[["r", "b"], {"edit_id": 10, "id": 3, "value": "B"}]], "row": {"a": "raw4", "id": "r", "revision": 8}} | {"draft": [[["r", "b"], {"edit_id": 10, "value": "B"}]], "error": null, "pending": [[["r", "b"], {"edit_id": 10, "id": 3, "value": "B"}]], "row": {"a": "raw4", "id": "r", "revision": 8}} | 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 ↗