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
"Learn" pages sidebar scrolls back to top on every page change #6409
Comments
Our students at https://labs.codeday.org will be taking a look at this issue (their first introduction to open source) :) |
Collaborator guide may be of interest to you and yours students, it explains a lot about the infrastructure aspect of the project |
FYI This is how we fixed this issue in the original redesign project |
@manishprivet there an "cool" ways to handle this problème it's to put navbar on On the example each item is a link so each time there are a click it's change url Enregistrement.de.l.ecran.2024-03-05.a.13.35.57.mov |
Agreed there @AugustinMauroy... one of the benefits of using Next <3 But we still need to add a scroll down logic for fresh page renders IMO |
Hey everyone, I'm part of the student group from CodeDay that was assigned this issue. The group includes Brian Van Der Sand, Jia Yang, and Steven Buks. We are all working to help solve this issue. |
Hi @Brianv707, good luck with this! I genuinely hope you'll enjoy contributing on this project, open source is amazing! |
I want to work on this if it's okay with @Brianv707 and his group. |
Thanks for your interest. We don't assign tickets if we can help it. Feel free to submit a pull request if you have time. |
Temporary workaround for nodejs#6409 Get more info here - nodejs#6675 Signed-off-by: abizek <abishekilango@protonmail.com>
URL:
Any page on https://beta-node-js-org.vercel.app/en/learn/
Browser Name:
Arc / Chrome
Browser Version:
122.0.6261.94 / 124.0.6334.0
Operating System:
MacOS Sonoma 14.3 / ArchLinux
How to reproduce the issue:
Tried taking a quick look at the code, it looks like it could be due to
[locale]/[[..path]]
routing.This issue looks very similar to this - it looks like every layout should have a unique key, which would reproduce the app router's built-in layout behavior.
The text was updated successfully, but these errors were encountered: