CSR (client side transition) not working on 404 pages
See original GitHub issueBug report
Describe the bug
Using a Link to go to a 404 page doesn’t work. The link is unresponsive, nothing happens on the browser.
You can reproduce this at https://nrn-v1-hyb-mst-aptd-gcms-lcz-sty-c1-peyfrlyfe.now.sh/fr/examples/built-in-utilities/errors-handling and click on the This is a client-side navigation (CSR)
link.
Note that using This is a normal navigation
link works as expected, but it uses a <a>
link instead.
To Reproduce
- Use
<Link>
fromnext/link
with href to a non-existing page - Try to click on it
Expected behavior
The link should redirect to a 404 page.
Screenshots
Video at https://youtu.be/mhJE5s-CIEE
Additional context
Reproduced on v9.4.1 to v9.4.4
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
React 404 page not working with CSSTransition
I need to apply a 404 error page to ReactJs with CSSTransition. This is working fine when I using it with react-router-dom Switch....
Read more >Compare and Contrast: CSR, SSR, and SSG in NextJS
Client -side rendering essentially means that the majority of the work (fetching data and creating HTML) is done by the browser, on demand,...
Read more >SSR vs SSG in Next.js – a practical overview for CTOs and devs
or when a user requests the page in a client-side transition by using next/link or next/router. The getServerSideProps function always returns ...
Read more >Next.js Pre-rendering and Data Fetching Methods - Pagepro
Learn about SSG, SSR, CSR, and ISR. The most popular pre-rendering and data fetching methods to build fast and SEO-friendly pages in ...
Read more >The Return of Server Side Routing - DEV Community
But all 3 approaches share the same model for how navigation should work. It is full-page and it is from the server. It...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can tell since the deployment doesn’t have internal Next.js changes from the latest canary and still has internal code for
v9.4.4
.For example, client page bundles are no longer nested under a directory with
BUILD_ID
on the latest canary of Next.js and the above deployment isThis issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.