FA-37452 / Table interactions / Member archive

Table expandable detail rows: detail eligibility · case 02

The table detail eligibility result violates the stipulated table expandable detail rows contract.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Detail rows have namespaced stable render keys, follow their visible expandable owner, never count as selectable data rows, use measured heights including zero, and contribute to total content height while expansion state output excludes hidden or ineligible rows.

Why this case matters

An offline table UI model isolates table expandable detail rows, 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
nonexpandable row	`{"data_count": 1, "expanded": [], "items": [{"height": 3, "key": ["data", "a"], "kind": "data", "owner": "a", "selectable": true}, {"height": 9, "key": ["detail", "a"], "kind": "detail", "owner": "a", "selectable": false}], "total": 12}`	`{"data_count": 1, "expanded": [], "items": [{"height": 3, "key": ["data", "a"], "kind": "data", "owner": "a", "selectable": true}], "total": 3}`	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.