You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short. Create a project with only nuxt rc.13 as a dependency.
Create a couple of pages which are longer than the viewable height of the browser. Put links to the pages down below the fold.
Scroll down to click on one of the links. The new page loads but the scroll position is still at the bottom of the page. This is not what anyone expects when navigating to a new "page". Scroll position should only be controlled by inclusion of a # in the URL typically.
This bug has been around since rc.7 at least.
Describe the bug
The user expects when clicking a link to a new "page" that the page will appear with the scroll position at the top of the page. For example, if you have a long page and click on a link in the footer, you may not notice the page content has changed because you can still only see the footer.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v16.17.0
3.0.0-rc.13
0.6.1
yarn@1.22.19
vite
nitro
-
-
Reproduction
https://github.com/chrisnoden/nuxt3-bug
In short. Create a project with only nuxt rc.13 as a dependency.
Create a couple of pages which are longer than the viewable height of the browser. Put links to the pages down below the fold.
Scroll down to click on one of the links. The new page loads but the scroll position is still at the bottom of the page. This is not what anyone expects when navigating to a new "page". Scroll position should only be controlled by inclusion of a # in the URL typically.
This bug has been around since rc.7 at least.
Describe the bug
The user expects when clicking a link to a new "page" that the page will appear with the scroll position at the top of the page. For example, if you have a long page and click on a link in the footer, you may not notice the page content has changed because you can still only see the footer.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: