Skip to content
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

Broken scroll behaviour involving links with fragments #3116

Closed
wodin opened this issue Dec 3, 2017 · 6 comments · May be fixed by harunpehlivan/gatsby#471, philipedin/gatsby#509, tejzpr/gatsby#25, tejzpr/gatsby#51 or harunpehlivan/gatsby#1055
Labels
help wanted Issue with a clear description that the community can help with. type: question or discussion Issue discussing or asking a question about Gatsby

Comments

@wodin
Copy link

wodin commented Dec 3, 2017

On https://www.gatsbyjs.org/docs/deploy-gatsby/, scrolled all the way to the top, click on one of the top three links, e.g. GitLab Pages. That scrolls down the page to the right section. Now click the browser's Back button and nothing happens, except the fragment is removed from the URL in the location bar.

I can reproduce this with latest Firefox and Chrome/Chromium on macOS, Linux and Windows 10 and Safari on macOS. I cannot reproduce this on Edge on Windows 10.

@ivorpad
Copy link
Contributor

ivorpad commented Dec 4, 2017

I can't reproduce this in Chrome v62.0.3202.94. All fine.

@wodin
Copy link
Author

wodin commented Dec 4, 2017

Not sure what to tell you. I can. On multiple machines/VMs/operating systems and browsers. So far the only one that I cannot reproduce this on is Edge, although I haven't tried IE or Opera, etc. I've just double checked the version of Chrome on a couple of the machines and it is v62.0.3202.94.

Here's a demonstration: https://gfycat.com/AmusedAdmirableCub

@markmichon
Copy link
Contributor

I couldn't reproduce in latest FF, but I am seeing the behavior in latest chrome on OSX.

@wodin
Copy link
Author

wodin commented Dec 4, 2017

Well at least I might not be hallucinating! :)

However, I can reproduce this on FF (57.0.1, some 32 bit and some 64 bit) on macOS, Linux and Windows. I have no idea what could be different about these machines compared to yours such that this doesn't happen for you.

If there's any other information I can provide to help get this diagnosed, let me know. Or is this perhaps something that Gatsby has no control over?

@m-allanson
Copy link
Contributor

I just tried this on macOS and couldn't replicate with Firefox, but could with Safari and Chrome.

Versions:

  • Firefox 59.0.2 (64-bit)
  • Safari 11.1 (13605.1.33.1.2)
  • Chrome 65.0.3325.181 (Official Build) (64-bit)

Fixes welcome if anyone can investigate further!

@m-allanson m-allanson added help wanted Issue with a clear description that the community can help with. type: question or discussion Issue discussing or asking a question about Gatsby labels Apr 18, 2018
@KyleAMathews
Copy link
Contributor

Due to the high volume of issues, we're closing out older ones without recent activity. Please open a new issue if you need help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment