Skip to content
Hazine

Error and recovery states

0 of 4 shipped. Nothing has shipped here yet. The list below is what this family will hold, and how each structure differs.

Planned 4

  • Inline Retry

    Sized to the region that failed rather than the page: single-row layout, retry button with a built-in pending state and attempt counter, and a switch to a Contact support link after repeated failures.

  • Error Boundary Panel

    Ships as an error boundary plus its fallback UI: catches render errors, exposes a reset callback, and separates user-facing recovery actions from a collapsed developer detail section.

  • Form Error Summary

    Navigational: each error is an anchor that focuses and scrolls to its field, and the summary itself takes focus on submit so keyboard and screen reader users land on it first.

  • Partial Failure List

    Mixed outcome rather than total failure: success count stays visible, failures are itemised with a per-row reason and retry, and rows leave the list as their retries succeed.