FA-37028 / Table interactions / Member archive

Merged cell rendering: overlap arbitration · case 03

The table overlap arbitration result violates the stipulated merged cell rendering contract.

Member previewVariant 3 · 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
partial overlap	`{"merges": [{"anchor": ["r0", "a"], "colspan": 2, "covered": [["r0", "b"], ["r1", "a"], ["r1", "b"]], "rowspan": 2, "value": "x"}, {"anchor": ["r1", "b"], "colspan": 2, "covered": [["r1", "c"], ["r2", "b"], ["r2", "c"]], "rowspan": 2, "value": "y"}], "plain": [["r0", "c"], ["r2", "a"]]}`	`{"merges": [{"anchor": ["r0", "a"], "colspan": 2, "covered": [["r0", "b"], ["r1", "a"], ["r1", "b"]], "rowspan": 2, "value": "x"}], "plain": [["r0", "c"], ["r1", "c"], ["r2", "a"], ["r2", "b"], ["r2", "c"]]}`	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.