FAILURE MAP
← Case archive

FA-37398 / Table interactions / Member archive

Table column drag transaction: self drop · case 03

The table self drop result violates the stipulated table column drag transaction contract.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Move selected columns as a schema-ordered block relative to a visible nonmoving target, preserve hidden columns, reject any locked or pane-incompatible member, and compute insertion after removing the whole source block.

Why this case matters

An offline table UI model isolates table column drag transaction, including adversarial row/column relationships.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
self drop on second["a", "c", "b"]["a", "b", "c"]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 ↗