FA-36849 / Table interactions / Member archive

Column track resolution: hidden track · case 04

The table hidden track result violates the stipulated column track resolution contract.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Resolve unique schema IDs in saved order then append unlisted visible columns; clamp widths to per-column bounds, keep explicit zero, compute prefix starts, omit a terminal resize handle, and use None for no terminal column.

Why this case matters

An offline table UI model isolates column track resolution, 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
multiple hidden	`{"handles": ["a", "b"], "ids": ["a", "b", "c"], "last": "c", "resizable": ["a", "b", "c"], "starts": {"a": 0, "b": 6, "c": 12}, "total": 18, "widths": {"a": 6, "b": 6, "c": 6}}`	`{"handles": [], "ids": ["c"], "last": "c", "resizable": ["c"], "starts": {"c": 0}, "total": 6, "widths": {"c": 6}}`	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.