FA-38199 / Table interactions / Member archive

Table row action targeting: bulk row order · case 04

The table bulk row order result violates the stipulated table row action targeting contract.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

A row action uses current row order, bulk selection only when the clicked row belongs to it and the action permits bulk, optional visible scope, default-deny per-action permissions, atomic busy/permission rejection, explicit empty scope, confirmation policy, and per-row revision snapshots.

Why this case matters

An offline table UI model isolates table row action targeting, including adversarial row/column relationships.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
ordered bulk selection	`{"action": "delete", "status": "confirm", "targets": [{"id": "c", "payload": {"v": 3}, "revision": 3}, {"id": "a", "payload": {"v": 4}, "revision": 1}]}`	`{"action": "delete", "status": "confirm", "targets": [{"id": "a", "payload": {"v": 4}, "revision": 1}, {"id": "c", "payload": {"v": 3}, "revision": 3}]}`	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.