FAILURE MAP
← Case archive

FA-33738 / Menu interactions / Member archive

Budget-truncated submenu lacks a visible truncation state · case 03

Budget-truncated submenu lacks a visible truncation state.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Nested menu providers consume shared row and depth budgets and charge visible descendants exactly once; cached rows still occupy presentation budget.

Why this case matters

Cascading and context menus require coherent command and session state as content changes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
truncate-signal contract{"rows": [0, 1], "truncated": false}{"rows": [0, 1], "truncated": true}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 ↗