You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Infrastructure: Restore Storybook stories excluded by native desktop crashes #4344
Restore native Storybook coverage currently excluded because of desktop-host fail-fast crashes. Parent: #4275. Bug follow-up to the delivered endpoint/pipeline milestones #4259/#4256.
The Storybook README documents native fail-fast termination (0xc0000409) as the reason. Current main manifests contain 168 macOS, 158 Windows, and 152 Win32 stories; exclusions are real missing coverage, not equivalent catalogs.
This audit verified source/configuration and generated catalogs, not a new interactive reproduction of each crash. Reproduce against the current resolved forks before attributing a root cause; do not infer that an old runtime diagnosis still explains every endpoint.
Reproduction
On the affected native endpoint, create a minimal isolated fixture or deliberately scoped local catalog for one excluded module at a time. Use the supported yarn storybook ... --<platform> lifecycle from apps/storybook, preserve exact process identity, and retain the first actionable native failure and story ID. Do not remove all exclusions from the normal PR lane before safe per-module qualification.
Acceptance criteria
Record a current minimal reproduction, resolved runtime/renderer/OS, first failing story, and native termination/error evidence for each excluded module/endpoint.
Fix or consume the owning native/runtime repair without suppressing the crash, replacing the native endpoint, or claiming a render-only proxy as coverage.
Add a regression that detects application termination as a failure and exercises the affected behavior, including delayed focus survival where relevant.
Remove each platform exclusion only after its native story cohort passes the full owned traversal/tests and cleanup on that endpoint.
Manifest/index checks and documentation accurately distinguish any remaining justified exclusions; require a linked issue and reason for each.
Windows/Win32 remain separate Fabric/Paper endpoints, other platforms preserve behavior, and native/package checks and necessary changesets pass.
Coordination
Restoring Accordion coverage unblocks the original focus-survival and accessibility cohorts (#4347/#4343). Coordinate #4349 for required-pipeline qualification. Native package/component fixes may also relate to #3971/#4274, but those broader issues do not currently track these exact catalog exclusions.
PR #4381 fixes the standalone Windows native Callout crash and removes that native-core catalog exclusion after the recorded Windows qualification (legacy/modern popup operations, flat Menu composition, and 100% scale anchor geometry). Windows Accordion and Win32 Accordion/ListItem exclusions remain, so this issue is only partially addressed and must remain open. Additional native-core Callout geometry/lifecycle/accessibility qualification is tracked by #4375.
Activity
JasonVMo commentedon Oct 16, 2026
PR #4381 fixes the standalone Windows native Callout crash and removes that native-core catalog exclusion after the recorded Windows qualification (legacy/modern popup operations, flat Menu composition, and 100% scale anchor geometry). Windows Accordion and Win32 Accordion/ListItem exclusions remain, so this issue is only partially addressed and must remain open. Additional native-core Callout geometry/lifecycle/accessibility qualification is tracked by #4375.