AI & Agent Dev Bug Sandbox Back to Radar

[CacheComponents] Stale Redirect Marker In Hidden Activity Route Causes Unintended Full-Page Navigation

When a route that calls redirect() behind Suspense is retained in a hidden React Activity (with cacheComponents enabled), the streamed __next-page-redirect DOM marker remains in the document. The navigate-reducer uses a document-wide getElementById check, so any subsequent same-origin Link click from the active route triggers a hard navigation instead of an SPA transition.

highConfidence 72%Next.js Affected V16.3.3 Affected V16.4.0-Canary.8 Affected V16.4.0-Canary.9

Origin Analysis

The navigate-reducer performs a global document.getElementById('__next-page-redirect') check. Because the lookup searches the whole document, it finds the redirect marker inside an inactive Activity subtree that is still part of the DOM (though hidden). This stale marker then incorrectly satisfies the hard-navigation condition, causing an unrelated Link click to perform a full-page navigation.

1. Build and start a Next.js app with cacheComponents enabled. 2. Visit a route that renders a component behind Suspense which calls redirect(). Next streams the #__next-page-redirect marker into the document. 3. Navigate away using <Link>. The previous route is retained in a hidden React Activity. 4. Verify that document.getElementById('__next-page-redirect') still finds the marker in the hidden subtree. 5. Click another unrelated same-origin <Link>. The click performs a full document navigation instead of an SPA navigation.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This fix assumes hidden Activities use display:none or equivalent that removes layout boxes. If a future version uses visibility:hidden or opacity:0 instead, getClientRects() may still return rects and the false positive would persist. Additionally, calling getClientRects() on every navigation may cause layout thrashing; for performance-critical paths, consider caching the active Activity reference or using the Activity-specific hidden attribute. Rollback recommendation: revert to the original document.getElementById check if this change introduces issues with legitimate redirect handling where the marker is not measured as visible.