FA-37504 / Table interactions / Member archive
Table row height measurement cache: column width validity · case 04
The table column width validity result violates the stipulated table row height measurement cache contract.
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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| changed widths | {"heights": {"a": 4}, "offsets": {"a": 0}, "remeasure": ["a"], "retained": {"a": {"generation": 2, "height": 4, "width_key": "old"}}, "total": 4} | {"heights": {"a": 10}, "offsets": {"a": 0}, "remeasure": ["a"], "retained": {"a": {"generation": 2, "height": 4, "width_key": "old"}}, "total": 10} | 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 ↗