FA-37019 / Table interactions / Member archive

Merged cell rendering: visible rowspan · case 04

The table visible rowspan result violates the stipulated merged cell rendering contract.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Merged rectangles are expressed in source coordinates, clipped to source bounds and visible rows/columns, rebased to the first visible cell, and accepted in declaration order only if disjoint; plain cells omit every accepted merged cell.

Why this case matters

An offline table UI model isolates merged cell rendering, 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
hidden anchor	`{"merges": [{"anchor": ["r2", "c"], "colspan": 1, "covered": [], "rowspan": 3, "value": "x"}], "plain": []}`	`{"merges": [{"anchor": ["r2", "c"], "colspan": 1, "covered": [], "rowspan": 1, "value": "x"}], "plain": []}`	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.