FA-37842 / Table interactions / Member archive

Table grouped row projection: group hidden members · case 02

The table group hidden members result violates the stipulated table grouped row projection contract.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Table group headers retain stable namespaced group keys distinct from labels, count visible members, derive tri-state selection over visible children, honor empty/collapsed group policies, and reset row striping within each group.

Why this case matters

An offline table UI model isolates table grouped row projection, 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 members	`[{"checked": false, "count": 3, "key": ["group", "g"], "kind": "group", "label": "G", "mixed": false}, {"group": "g", "key": ["row", "a"], "kind": "row", "row": {"id": "a"}, "stripe": 0}, {"group": "g", "key": ["row", "b"], "kind": "row", "row": {"id": "b"}, "stripe": 1}, {"group": "g", "key": ["row", "c"], "kind": "row", "row": {"id": "c"}, "stripe": 0}]`	`[{"checked": false, "count": 1, "key": ["group", "g"], "kind": "group", "label": "G", "mixed": false}, {"group": "g", "key": ["row", "c"], "kind": "row", "row": {"id": "c"}, "stripe": 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.