FA-37537 / Table interactions / Member archive

Table row height measurement cache: stale measurement prune · case 02

The table stale measurement prune result violates the stipulated table row height measurement cache contract.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Measured row heights are keyed by stable row ID plus row-data generation and column-width fingerprint. Invalid measurements use an estimate, minimum applies before detail height, positions are ordered prefixes, and stale row measurements are pruned.

Why this case matters

An offline table UI model isolates table row height measurement cache, 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
zero and stale id	`{"heights": {"a": 0}, "offsets": {"a": 0}, "remeasure": [], "retained": {"a": {"generation": 2, "height": 0, "width_key": "w"}, "gone": {"generation": 2, "height": 7, "width_key": "w"}}, "total": 0}`	`{"heights": {"a": 0}, "offsets": {"a": 0}, "remeasure": [], "retained": {"a": {"generation": 2, "height": 0, "width_key": "w"}}, "total": 0}`	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.