Suspense decides what to show when something suspends, and the kind of update decides which outcome React accepts:
- Urgent update (a plain
setStatefrom a click): the user expects an immediate response, so React commits right away. If a boundary that's already showing content suspends, React hides that content and shows the fallback again. Navigating with a boundary near the root swaps the whole page for a spinner. - Transition (
startTransition,useTransition): the update is allowed to wait. If committing it would hide already-revealed content behind a fallback, React doesn't commit. The old UI stays on screen and interactive, and the new UI appears once the data has loaded. WithuseTransition,isPendingistruemeanwhile, so you can dim the page or show a progress bar. useDeferredValue: the background re-render with the new value is a Transition too. If it suspends, the user keeps seeing the stale value instead of a fallback.
Two limits matter:
- New boundaries still show their fallbacks. A Transition only waits long enough not to hide what's already on screen. A
<Suspense>that appears for the first time in this update shows its fallback immediately, so the new page can render its shell while its slower sections load. - Different content should reset. When the user navigates to another profile, the old profile staying visible may be wrong. Give the boundary (or a parent)
key={userId}: a new key makes it a new boundary, so it shows its fallback even in a Transition.
Only non-urgent updates get this treatment; React never delays an urgent render. That's why Suspense-enabled routers wrap navigations in Transitions by default, and why refetching with use stores the new promise in state inside startTransition.