-
Notifications
You must be signed in to change notification settings - Fork 26.3k
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
[v7] Sometimes Links stop working. #5478
Comments
Not sure, but it seems to happen at some point after a hot reload. |
I noticed the same thing after updating to 7 but it happens in development mode only. I am not sure if it is related to HMR or not. My observation is that the server stop compiling the page and the link hangs. Thankfully refresh fixes the issue. |
I can attest to that too... dev only, super random, page reload fixes it |
+1 |
Things missing:
We have a whole test suite that is literally clicking around every feature in chrome while in development mode: https://github.com/zeit/next.js/blob/canary/test/integration/basic/test/client-navigation.js |
reopen issue
me too, reopen issue? |
seeing this too @timneutkens should I open a new issue with correct Issue Template and not quite sure how to provide reproduction instructions because the Links seem to just stop working after either a certain amount of time, or maybe after clicking around a bit? |
I am having the same issue as well. The issue seems to appear after the user is inactive on the webpage after a while. |
Same issue here. It's hard to consistently reproduce as it only seems to happen after a certain amount of time and pretty randomly. The issue goes away if you reload the page. Not sure if this will help anyone debugging but if you grab Router.events.on('routeChangeStart', url => {
console.log('Navigating to:', url);
});
Router.events.on('routeChangeComplete', url => {
console.log('Completed navigation to: ', url);
}); @timneutkens Could you reopen this please 🙂 |
I'm going to quote myself: "
We have a whole test suite that is literally clicking around every feature in chrome while in development mode: https://github.com/zeit/next.js/blob/canary/test/integration/basic/test/client-navigation.js I'm not going to reopen this issue based on what I posted earlier. I'd be happy to take a look if there is a clear and concise reproduction. |
@timneutkens I completely understand why we need a reproduction scenario but I do believe none of us can do that as the issue is happening randomly without any clear steps to do. When the HMR drops in and does it work suddenly links stop working and I refresh and bingo; it's resolved. Happen on a daily basis like 10 times during development and what I use is the same format I was using in the previous version. I know it is hard to debug without a proper reproduction scenario maybe some of us need to spend more time investigating and coming up with it. |
I am using next-routes and material-ui which I think could potentially be a source of the problem. |
@timneutkens Thanks, I was able to reproduce with reproduction steps. Have opened a new issue here #5598 |
@iamandyk I am not using material-ui and I still see the problem |
@iamandyk @ahmadalfy No next-routes, and no material-ui over here but I have the same problem. Everything works perfect for a few minutes, and then, random links stop working on client side with no errors. |
Same here, it's really annoying sometimes.. |
same issue |
+1 |
1 similar comment
+1 |
Instead of posting Assuming you're having the same issue as @malimccalla you can track #5598 |
So I have a similar issue, but I think I found a strange solution that might illuminate the problem. Hope this helps, if not let me know. First let me give @timneutkens what he asked for: Bug reportDescribe the bug(using: To ReproduceI'm putting together a new portfolio, and ran into the issue. Created a specific branch just to replicate it here. If Expected behaviorClicking the link would navigate me to the route described in the WorkaroundYou will notice in PS: new to next.js. |
I am also having this issue. Looks like the Links are intercepting the click but do not take to the desired page. Links are created as
Then I tested the click intercept with
When I click on my Link I can see |
Try next@canary |
@timneutkens The problem is, this happens at random times. Anyway, I will give it a try and let you know asap. Thanks. |
I am still having issues with this. |
I'm also having issues with this. It happens randomly but is fixed after a hard refresh. |
Please create a new issue with a clear and concise reproduction. Thanks 🙏 |
Happens all the time, after a period of inactivity (10 mins) or multiple hot reloads stops working in development mode. |
Hi everyone, if you're still experiencing this issue on v8 please file a new issue. It is not feasible for us to track issue in old threads with outdated context. Thank you for your cooperation. |
I don't have much info. I updated to v7, and every once in a while
<Link>
s in the entire app stop being clickable, and nothing happens when clicking them.I'm not doing anything special, just
<Link href="...">
and the only child elements in my Links are plain<a>
tags with no attributes, except forclassName
when I want to style them.F.e.:
Somethings up. But not sure how to reproduce.
The text was updated successfully, but these errors were encountered: