FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-8701

Overlay dismissal stack: Unmounting one layer retains only the removed layer · case 01

Unmounting one layer retains only the removed layer.

Overlay interactions● Open access↗
FA-8702

Overlay dismissal stack: Unmounting one layer retains only the removed layer · case 02

Unmounting one layer retains only the removed layer.

Overlay interactions◈ Members↗
FA-8703

Overlay dismissal stack: Unmounting one layer retains only the removed layer · case 03

Unmounting one layer retains only the removed layer.

Overlay interactions◈ Members↗
FA-8704

Overlay dismissal stack: Unmounting one layer retains only the removed layer · case 04

Unmounting one layer retains only the removed layer.

Overlay interactions◈ Members↗
FA-8705

Overlay dismissal stack: Unmounting one layer retains only the removed layer · case 05

Unmounting one layer retains only the removed layer.

Overlay interactions◈ Members↗
FA-8706

Toast queue lifecycle: Equal-message toasts with different identities are collapsed · case 01

Equal-message toasts with different identities are collapsed.

Notification interfaces● Open access↗
FA-8707

Toast queue lifecycle: Equal-message toasts with different identities are collapsed · case 02

Equal-message toasts with different identities are collapsed.

Notification interfaces◈ Members↗
FA-8708

Toast queue lifecycle: Equal-message toasts with different identities are collapsed · case 03

Equal-message toasts with different identities are collapsed.

Notification interfaces◈ Members↗
FA-8709

Toast queue lifecycle: Equal-message toasts with different identities are collapsed · case 04

Equal-message toasts with different identities are collapsed.

Notification interfaces◈ Members↗
FA-8710

Toast queue lifecycle: Equal-message toasts with different identities are collapsed · case 05

Equal-message toasts with different identities are collapsed.

Notification interfaces◈ Members↗
FA-8711

Toast queue lifecycle: Capacity eviction removes the newest notifications · case 01

Capacity eviction removes the newest notifications.

Notification interfaces● Open access↗
FA-8712

Toast queue lifecycle: Capacity eviction removes the newest notifications · case 02

Capacity eviction removes the newest notifications.

Notification interfaces◈ Members↗
FA-8713

Toast queue lifecycle: Capacity eviction removes the newest notifications · case 03

Capacity eviction removes the newest notifications.

Notification interfaces◈ Members↗
FA-8714

Toast queue lifecycle: Capacity eviction removes the newest notifications · case 04

Capacity eviction removes the newest notifications.

Notification interfaces◈ Members↗
FA-8715

Toast queue lifecycle: Capacity eviction removes the newest notifications · case 05

Capacity eviction removes the newest notifications.

Notification interfaces◈ Members↗
FA-8716

Toast queue lifecycle: Updating one toast overwrites all toast messages · case 01

Updating one toast overwrites all toast messages.

Notification interfaces● Open access↗
FA-8717

Toast queue lifecycle: Updating one toast overwrites all toast messages · case 02

Updating one toast overwrites all toast messages.

Notification interfaces◈ Members↗
FA-8718

Toast queue lifecycle: Updating one toast overwrites all toast messages · case 03

Updating one toast overwrites all toast messages.

Notification interfaces◈ Members↗
FA-8719

Toast queue lifecycle: Updating one toast overwrites all toast messages · case 04

Updating one toast overwrites all toast messages.

Notification interfaces◈ Members↗
FA-8720

Toast queue lifecycle: Updating one toast overwrites all toast messages · case 05

Updating one toast overwrites all toast messages.

Notification interfaces◈ Members↗
FA-8721

Toast queue lifecycle: Dismissing a toast retains the dismissed toast and removes others · case 01

Dismissing a toast retains the dismissed toast and removes others.

Notification interfaces● Open access↗
FA-8722

Toast queue lifecycle: Dismissing a toast retains the dismissed toast and removes others · case 02

Dismissing a toast retains the dismissed toast and removes others.

Notification interfaces◈ Members↗
FA-8723

Toast queue lifecycle: Dismissing a toast retains the dismissed toast and removes others · case 03

Dismissing a toast retains the dismissed toast and removes others.

Notification interfaces◈ Members↗
FA-8724

Toast queue lifecycle: Dismissing a toast retains the dismissed toast and removes others · case 04

Dismissing a toast retains the dismissed toast and removes others.

Notification interfaces◈ Members↗
FA-8725

Toast queue lifecycle: Dismissing a toast retains the dismissed toast and removes others · case 05

Dismissing a toast retains the dismissed toast and removes others.

Notification interfaces◈ Members↗
FA-8726

Toast queue lifecycle: Clear-all removes only the newest toast · case 01

Clear-all removes only the newest toast.

Notification interfaces● Open access↗
FA-8727

Toast queue lifecycle: Clear-all removes only the newest toast · case 02

Clear-all removes only the newest toast.

Notification interfaces◈ Members↗
FA-8728

Toast queue lifecycle: Clear-all removes only the newest toast · case 03

Clear-all removes only the newest toast.

Notification interfaces◈ Members↗
FA-8729

Toast queue lifecycle: Clear-all removes only the newest toast · case 04

Clear-all removes only the newest toast.

Notification interfaces◈ Members↗
FA-8730

Toast queue lifecycle: Clear-all removes only the newest toast · case 05

Clear-all removes only the newest toast.

Notification interfaces◈ Members↗
FA-8731

Progress indicator representation: Indeterminate progress is announced as zero completion · case 01

Indeterminate progress is announced as zero completion.

Assistive semantics● Open access↗
FA-8732

Progress indicator representation: Indeterminate progress is announced as zero completion · case 02

Indeterminate progress is announced as zero completion.

Assistive semantics◈ Members↗
FA-8733

Progress indicator representation: Indeterminate progress is announced as zero completion · case 03

Indeterminate progress is announced as zero completion.

Assistive semantics◈ Members↗
FA-8734

Progress indicator representation: Indeterminate progress is announced as zero completion · case 04

Indeterminate progress is announced as zero completion.

Assistive semantics◈ Members↗
FA-8735

Progress indicator representation: Indeterminate progress is announced as zero completion · case 05

Indeterminate progress is announced as zero completion.

Assistive semantics◈ Members↗
FA-8736

Progress indicator representation: Out-of-range progress exposes invalid accessible values · case 01

Out-of-range progress exposes invalid accessible values.

Assistive semantics● Open access↗
FA-8737

Progress indicator representation: Out-of-range progress exposes invalid accessible values · case 02

Out-of-range progress exposes invalid accessible values.

Assistive semantics◈ Members↗
FA-8738

Progress indicator representation: Out-of-range progress exposes invalid accessible values · case 03

Out-of-range progress exposes invalid accessible values.

Assistive semantics◈ Members↗
FA-8739

Progress indicator representation: Out-of-range progress exposes invalid accessible values · case 04

Out-of-range progress exposes invalid accessible values.

Assistive semantics◈ Members↗
FA-8740

Progress indicator representation: Out-of-range progress exposes invalid accessible values · case 05

Out-of-range progress exposes invalid accessible values.

Assistive semantics◈ Members↗
FA-8741

Progress indicator representation: Progress percentage ignores a nonzero range origin · case 01

Progress percentage ignores a nonzero range origin.

Assistive semantics● Open access↗
FA-8742

Progress indicator representation: Progress percentage ignores a nonzero range origin · case 02

Progress percentage ignores a nonzero range origin.

Assistive semantics◈ Members↗
FA-8743

Progress indicator representation: Progress percentage ignores a nonzero range origin · case 03

Progress percentage ignores a nonzero range origin.

Assistive semantics◈ Members↗
FA-8744

Progress indicator representation: Progress percentage ignores a nonzero range origin · case 04

Progress percentage ignores a nonzero range origin.

Assistive semantics◈ Members↗
FA-8745

Progress indicator representation: Progress percentage ignores a nonzero range origin · case 05

Progress percentage ignores a nonzero range origin.

Assistive semantics◈ Members↗
FA-8746

Progress indicator representation: A completed zero-span range is announced as unstarted · case 01

A completed zero-span range is announced as unstarted.

Assistive semantics● Open access↗
FA-8747

Progress indicator representation: A completed zero-span range is announced as unstarted · case 02

A completed zero-span range is announced as unstarted.

Assistive semantics◈ Members↗
FA-8748

Progress indicator representation: A completed zero-span range is announced as unstarted · case 03

A completed zero-span range is announced as unstarted.

Assistive semantics◈ Members↗
FA-8749

Progress indicator representation: A completed zero-span range is announced as unstarted · case 04

A completed zero-span range is announced as unstarted.

Assistive semantics◈ Members↗
FA-8750

Progress indicator representation: A completed zero-span range is announced as unstarted · case 05

A completed zero-span range is announced as unstarted.

Assistive semantics◈ Members↗
FA-8751

Progress indicator representation: Completed progress remains announced as busy · case 01

Completed progress remains announced as busy.

Assistive semantics● Open access↗
FA-8752

Progress indicator representation: Completed progress remains announced as busy · case 02

Completed progress remains announced as busy.

Assistive semantics◈ Members↗
FA-8753

Progress indicator representation: Completed progress remains announced as busy · case 03

Completed progress remains announced as busy.

Assistive semantics◈ Members↗
FA-8754

Progress indicator representation: Completed progress remains announced as busy · case 04

Completed progress remains announced as busy.

Assistive semantics◈ Members↗
FA-8755

Progress indicator representation: Completed progress remains announced as busy · case 05

Completed progress remains announced as busy.

Assistive semantics◈ Members↗
FA-8756

Resizable panel constraint handling: Disabled resizing unexpectedly collapses the panel · case 01

Disabled resizing unexpectedly collapses the panel.

Direct manipulation● Open access↗
FA-8757

Resizable panel constraint handling: Disabled resizing unexpectedly collapses the panel · case 02

Disabled resizing unexpectedly collapses the panel.

Direct manipulation◈ Members↗
FA-8758

Resizable panel constraint handling: Disabled resizing unexpectedly collapses the panel · case 03

Disabled resizing unexpectedly collapses the panel.

Direct manipulation◈ Members↗
FA-8759

Resizable panel constraint handling: Disabled resizing unexpectedly collapses the panel · case 04

Disabled resizing unexpectedly collapses the panel.

Direct manipulation◈ Members↗
FA-8760

Resizable panel constraint handling: Disabled resizing unexpectedly collapses the panel · case 05

Disabled resizing unexpectedly collapses the panel.

Direct manipulation◈ Members↗
FA-8761

Resizable panel constraint handling: Trailing-edge handles resize in the wrong visual direction · case 01

Trailing-edge handles resize in the wrong visual direction.

Direct manipulation● Open access↗
FA-8762

Resizable panel constraint handling: Trailing-edge handles resize in the wrong visual direction · case 02

Trailing-edge handles resize in the wrong visual direction.

Direct manipulation◈ Members↗
FA-8763

Resizable panel constraint handling: Trailing-edge handles resize in the wrong visual direction · case 03

Trailing-edge handles resize in the wrong visual direction.

Direct manipulation◈ Members↗
FA-8764

Resizable panel constraint handling: Trailing-edge handles resize in the wrong visual direction · case 04

Trailing-edge handles resize in the wrong visual direction.

Direct manipulation◈ Members↗
FA-8765

Resizable panel constraint handling: Trailing-edge handles resize in the wrong visual direction · case 05

Trailing-edge handles resize in the wrong visual direction.

Direct manipulation◈ Members↗
FA-8766

Resizable panel constraint handling: Resize deltas replace the absolute panel size · case 01

Resize deltas replace the absolute panel size.

Direct manipulation● Open access↗
FA-8767

Resizable panel constraint handling: Resize deltas replace the absolute panel size · case 02

Resize deltas replace the absolute panel size.

Direct manipulation◈ Members↗
FA-8768

Resizable panel constraint handling: Resize deltas replace the absolute panel size · case 03

Resize deltas replace the absolute panel size.

Direct manipulation◈ Members↗
FA-8769

Resizable panel constraint handling: Resize deltas replace the absolute panel size · case 04

Resize deltas replace the absolute panel size.

Direct manipulation◈ Members↗
FA-8770

Resizable panel constraint handling: Resize deltas replace the absolute panel size · case 05

Resize deltas replace the absolute panel size.

Direct manipulation◈ Members↗
FA-8771

Resizable panel constraint handling: Panels shrink below their minimum usable size · case 01

Panels shrink below their minimum usable size.

Direct manipulation● Open access↗
FA-8772

Resizable panel constraint handling: Panels shrink below their minimum usable size · case 02

Panels shrink below their minimum usable size.

Direct manipulation◈ Members↗
FA-8773

Resizable panel constraint handling: Panels shrink below their minimum usable size · case 03

Panels shrink below their minimum usable size.

Direct manipulation◈ Members↗
FA-8774

Resizable panel constraint handling: Panels shrink below their minimum usable size · case 04

Panels shrink below their minimum usable size.

Direct manipulation◈ Members↗
FA-8775

Resizable panel constraint handling: Panels shrink below their minimum usable size · case 05

Panels shrink below their minimum usable size.

Direct manipulation◈ Members↗
FA-8776

Resizable panel constraint handling: Panels expand beyond their maximum size · case 01

Panels expand beyond their maximum size.

Direct manipulation● Open access↗
FA-8777

Resizable panel constraint handling: Panels expand beyond their maximum size · case 02

Panels expand beyond their maximum size.

Direct manipulation◈ Members↗
FA-8778

Resizable panel constraint handling: Panels expand beyond their maximum size · case 03

Panels expand beyond their maximum size.

Direct manipulation◈ Members↗
FA-8779

Resizable panel constraint handling: Panels expand beyond their maximum size · case 04

Panels expand beyond their maximum size.

Direct manipulation◈ Members↗
FA-8780

Resizable panel constraint handling: Panels expand beyond their maximum size · case 05

Panels expand beyond their maximum size.

Direct manipulation◈ Members↗
FA-8781

Split-pane divider allocation: Divider width is counted as usable pane area · case 01

Divider width is counted as usable pane area.

Viewport layout● Open access↗
FA-8782

Split-pane divider allocation: Divider width is counted as usable pane area · case 02

Divider width is counted as usable pane area.

Viewport layout◈ Members↗
FA-8783

Split-pane divider allocation: Divider width is counted as usable pane area · case 03

Divider width is counted as usable pane area.

Viewport layout◈ Members↗
FA-8784

Split-pane divider allocation: Divider width is counted as usable pane area · case 04

Divider width is counted as usable pane area.

Viewport layout◈ Members↗
FA-8785

Split-pane divider allocation: Divider width is counted as usable pane area · case 05

Divider width is counted as usable pane area.

Viewport layout◈ Members↗
FA-8786

Split-pane divider allocation: Impossible minimum constraints overflow a narrow container · case 01

Impossible minimum constraints overflow a narrow container.

Viewport layout● Open access↗
FA-8787

Split-pane divider allocation: Impossible minimum constraints overflow a narrow container · case 02

Impossible minimum constraints overflow a narrow container.

Viewport layout◈ Members↗
FA-8788

Split-pane divider allocation: Impossible minimum constraints overflow a narrow container · case 03

Impossible minimum constraints overflow a narrow container.

Viewport layout◈ Members↗
FA-8789

Split-pane divider allocation: Impossible minimum constraints overflow a narrow container · case 04

Impossible minimum constraints overflow a narrow container.

Viewport layout◈ Members↗
FA-8790

Split-pane divider allocation: Impossible minimum constraints overflow a narrow container · case 05

Impossible minimum constraints overflow a narrow container.

Viewport layout◈ Members↗
FA-8791

Split-pane divider allocation: Compressed panes ignore their relative minimum sizes · case 01

Compressed panes ignore their relative minimum sizes.

Viewport layout● Open access↗
FA-8792

Split-pane divider allocation: Compressed panes ignore their relative minimum sizes · case 02

Compressed panes ignore their relative minimum sizes.

Viewport layout◈ Members↗
FA-8793

Split-pane divider allocation: Compressed panes ignore their relative minimum sizes · case 03

Compressed panes ignore their relative minimum sizes.

Viewport layout◈ Members↗
FA-8794

Split-pane divider allocation: Compressed panes ignore their relative minimum sizes · case 04

Compressed panes ignore their relative minimum sizes.

Viewport layout◈ Members↗
FA-8795

Split-pane divider allocation: Compressed panes ignore their relative minimum sizes · case 05

Compressed panes ignore their relative minimum sizes.

Viewport layout◈ Members↗
FA-8796

Split-pane divider allocation: The first pane shrinks below its minimum · case 01

The first pane shrinks below its minimum.

Viewport layout● Open access↗
FA-8797

Split-pane divider allocation: The first pane shrinks below its minimum · case 02

The first pane shrinks below its minimum.

Viewport layout◈ Members↗
FA-8798

Split-pane divider allocation: The first pane shrinks below its minimum · case 03

The first pane shrinks below its minimum.

Viewport layout◈ Members↗
FA-8799

Split-pane divider allocation: The first pane shrinks below its minimum · case 04

The first pane shrinks below its minimum.

Viewport layout◈ Members↗
FA-8800

Split-pane divider allocation: The first pane shrinks below its minimum · case 05

The first pane shrinks below its minimum.

Viewport layout◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗