Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Docs: Clicking on Learn Next.js button leads to page with missing text [2 pull requests, 3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#89170•Fetched 2026-04-08 02:03:15
View on GitHub
Comments
3
Participants
4
Timeline
10
Reactions
1
Author
henrikvilhelmberglundhenrikvilhelmberglund
Participants
eps1loneps1longithub-actions[bot]github-actions[bot]henrikvilhelmberglundhenrikvilhelmberglundicyJosephicyJoseph
Assignees
icyJosephicyJoseph
Timeline (top)
commented ×3assigned ×1closed ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #89339: segment cache: add test for passing unawaited promise to context provider

Description (problem / solution / changelog)

Adds a failing test proving that if the RSC response from a prefetch contains an unresolved promise, navigating to the page will cause the Suspense boundary wrapping the use of that promise to remain in fallback state indefinitely.

This appears to have regressed in e9a03ac12cfe3c3fb6b16db42ade06e7382b9018, though the theory is that this is just uncovering a React bug rather than causing the issue.

Fixed via https://github.com/facebook/react/pull/35839

Closes #89170

Changed files

  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/layout.tsx (added, +9/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/learn/layout.tsx (added, +9/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/learn/page.tsx (added, +12/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/lib/get-user.ts (added, +12/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/page.tsx (added, +12/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/user-card-shell.tsx (added, +12/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/user-card.tsx (added, +9/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/app/user-provider.tsx (added, +29/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/next.config.js (added, +8/-0)
  • test/e2e/app-dir/segment-cache/prefetch-partial-rsc/prefetch-partial-rsc.test.ts (added, +17/-0)
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

https://nextjs.org/ - clicking on Learn Next.js leads to a page with missing text.

The text appears after a F5 on the /learn page

Is there any context that might help us understand?

Repro:

  1. go to nextjs.org - F5 if any previous navigation
  2. click Learn Next.js Result: page with missing text Expected: page without missing text

Screenshot: Image

After F5: Image

Does the docs page already exist? Please link to it.

No response

extent analysis

TL;DR

  • The issue with missing text on the Next.js Learn page may be resolved by refreshing the page or checking the page's caching and rendering mechanism.

Guidance

  • Verify if the issue is related to client-side caching by checking the page's behavior in a private browsing mode or after clearing the browser cache.
  • Investigate the page's rendering mechanism to ensure that all necessary components are loaded correctly before the page is displayed.
  • Check the page's source code to see if there are any conditional statements or asynchronous operations that might be causing the text to be missing initially.
  • Test the page in different environments or browsers to determine if the issue is specific to a particular setup.

Notes

  • The provided screenshots suggest that the issue might be related to how the page is rendered or cached, but more information about the page's implementation would be necessary to provide a definitive solution.
  • The fact that the text appears after a refresh (F5) suggests that the issue might be related to the initial loading of the page rather than a problem with the page's content itself.

Recommendation

  • Apply workaround: Refresh the page or check the caching mechanism, as this seems to resolve the issue temporarily, and further investigation is needed to determine the root cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING