FAILURE MAP
← Case archive

FA-8938 / Table interactions / Member archive

Multi-column sort interaction: Reactivating ascending sort does not reverse direction · case 03

Reactivating ascending sort does not reverse direction.

Member previewVariant 3 · 3 implementations · 11 checks per implementation

Case contract

New sort is ascending; activation cycles ascending to descending to removed when allowed; single mode replaces all sorts; multi mode preserves priorities when changing direction.

Why this case matters

A deterministic model of multi-column sort interaction; this isolates one interface invariant without requiring a browser.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
reverse[["a", "asc"]][["a", "desc"]]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 ↗