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
@lttr I checked your issue in multiple browsers and the final feedback is given below.
Feedback
The URL hash(#) will automatically change if you cross the heading 50%(approximately) of your device view-height. when you see the heading "Next Steps" it doesn't cross 50% view-height so the URL hash remains in "#using-vue-from-cdn". After go forward & go back browser shows you the "Using Vue from CDN" headling because the last hash history is "#using-vue-from-cdn".
After go forward & go back multiple times firefox browser shows you the top of the page. Because firefox remove your last hash history. This "scroll-linked positioning effect not work well in firefox" and show a warning in the console [reference1]. You don't see this issue in chrome/other browser.
Thank you for the investigation. My main point is that it is unfortunate, that the behavior is worse than if it the website would be static HTML site. There might be issues with Firefox, but as far as I understand your answer it looks like the issue will be the same for any content on a page which has no headings. Binding scroll position to hash part of the URL is nice for linking to specific parts of an article but it is definitely not saving the scroll position, which might be different.
A typical scenario is when you click a link, chect the other page or website and then after a couple of moments you hit back button to continue reading the original page. At least for me it is very confusing to not have the original page in the exact same position.
I expect to land on the same scroll position as I was before on a page A, when I use a back button on page B.
I end up on the top of the page A or even at a different position, instead of on the scroll position I was before.
Reproduction
Expected behavior
Ideally the scroll position would be preserved at the exact same position, as it is done on plain HTML by browsers.
The issue is not present when I disable JavaScript in DevTools.
Environment
Browser: Firefox 112
OS: Pop_OS (Ubuntu) 22.04
The text was updated successfully, but these errors were encountered: