-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Docs: Add prefetching guide #80152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: canary
Are you sure you want to change the base?
Docs: Add prefetching guide #80152
Conversation
|
### Disabling prefetching on hover | ||
|
||
- How do you disable prefetch on hover? https://github.com/vercel/next.js/discussions/24437 | ||
- Use your own Ejected Link component |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Historically, this was a problem in pages router, because disabling prefetch, kept the on-hover behavior.
In this case, the root issue was "too many prefetches", that lead people to opt-into prefetch false, but, perhaps unexpectedly, still kept the on-hover issue.
In App Router, prefetch false, disables on-hover too. So that problem is solved. However, we have the opposite problem, so to speak. People who did want to disable prefetching on the viewport, but still prefetch on hover.
The proposal up above, to do a Hover-triggered prefetch
~ does cover the use case, so I think we can drops this third section altogether.
### Disabling prefetching on hover | |
- How do you disable prefetch on hover? https://github.com/vercel/next.js/discussions/24437 | |
- Use your own Ejected Link component |
Co-authored-by: Joseph <[email protected]>
Co-authored-by: Joseph <[email protected]>
…xt.js into docs-prefetching-guide
All broken links are now fixed, thank you! |
To do:
onClick
androuter.push
- @icyJoseph