Link hover and useParam
Answered
Dusky-capped Flycatcher posted this in #help-forum
Dusky-capped FlycatcherOP
Hello
I just upgraded to Next 14 and was hit by
https://github.com/vercel/next.js/issues/58788 ... which is closed and meant to be fixed since 14.1.1 if I am not mistaken. It's quite visible for me because I have plots with animation which are constantly redrawing as soon as I hover a
Do you guys really see this fixed? 😳
I just upgraded to Next 14 and was hit by
https://github.com/vercel/next.js/issues/58788 ... which is closed and meant to be fixed since 14.1.1 if I am not mistaken. It's quite visible for me because I have plots with animation which are constantly redrawing as soon as I hover a
<Link>. If I remove the hooks from the component, they stop redrawing.Do you guys really see this fixed? 😳
Answered by Dusky-capped Flycatcher
OK, I guess it's normal. The confusion comes from the naming of the canary versions. I sorted this out by looking at the git tree in the repo.
Actually the 14.1.4 version is released from the
I don't really understand the rationales for the digits before the
See attached screenshot where we switch from
I can confirm that the very test case used in the GitHub issue still demonstrates the issue with
Actually the 14.1.4 version is released from the
next-14-1 branch while all canary versions come from the canary (main) branch.I don't really understand the rationales for the digits before the
canary name as there seems to be no clue whatsoever with the official release being prepared with these canary builds... Presumably some project management decision?See attached screenshot where we switch from
v14.1.2-canary.7 to v14.2.0-canary.0 with no apparent reason.I can confirm that the very test case used in the GitHub issue still demonstrates the issue with
14.1.4 but is no longer present in 14.2.0-canary.343 Replies
Dusky-capped FlycatcherOP
OK, I guess it's normal. The confusion comes from the naming of the canary versions. I sorted this out by looking at the git tree in the repo.
Actually the 14.1.4 version is released from the
I don't really understand the rationales for the digits before the
See attached screenshot where we switch from
I can confirm that the very test case used in the GitHub issue still demonstrates the issue with
Actually the 14.1.4 version is released from the
next-14-1 branch while all canary versions come from the canary (main) branch.I don't really understand the rationales for the digits before the
canary name as there seems to be no clue whatsoever with the official release being prepared with these canary builds... Presumably some project management decision?See attached screenshot where we switch from
v14.1.2-canary.7 to v14.2.0-canary.0 with no apparent reason.I can confirm that the very test case used in the GitHub issue still demonstrates the issue with
14.1.4 but is no longer present in 14.2.0-canary.34Answer
Yes, all 14.1.x (x > 0) versions do not have all the canary changes
They only have selected changes to fix big bugs