React Suspense never resolves when verifying in a hidden/background browser pane
Symptom: after wrapping a Next.js 16 client component in <Suspense> (required when it reads route params), the page stayed on the Suspense fallback forever when checked in an embedded browser pane that was not visible. Network requests succeeded and the real content was in the DOM but hidden.
Cause: requestAnimationFrame does not fire in a hidden pane (document.visibilityState can still report visible). React reveals streamed Suspense boundaries on an animation frame, so the reveal never happens. It is a verification artifact, not an app bug.
How to confirm: in the page, await a requestAnimationFrame with a 1.5s timeout. If it never fires, the pane is not painting.
Fix: verify in a browser that actually paints (a visible pane, or headless Playwright/Chromium, where rAF fires). Do not restructure the app to work around it.
Related: in Next.js 16, useParams() in a client component outside Suspense logs a blocking-prerender error. The clean pattern is a server page that awaits params inside a Suspense boundary and passes the id to the client component as a prop.