FAILURE MAP
← Case archive

FA-32844 / Menu interactions / Member archive

Popup cleanup reverses registration order instead of menu ancestor depth · case 04

Popup cleanup reverses registration order instead of menu ancestor depth.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Each popup owns subscriptions, timers, content and anchors; teardown releases exactly owned resources and is safe when repeated.

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
child-order contract[4, "root", "child"][4, "child", "root"]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 ↗