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

fix(gatsby-react-router-scroll): Respect hash as source of truth for scroll position (#28555) #28560

Closed
wants to merge 1 commit into from

Conversation

gatsbybot
Copy link
Collaborator

Backporting #28555 to the 2.28 release branch

(cherry picked from commit a066a71)

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 9, 2020
Copy link
Contributor

@sidharthachatterjee sidharthachatterjee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💥

@sidharthachatterjee sidharthachatterjee removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 9, 2020
@pieh pieh marked this pull request as draft December 9, 2020 15:20
@pieh
Copy link
Contributor

pieh commented Dec 9, 2020

Marking as draft for now due to my concerns (mostly make sure that we don't trade one problem for another here). We also recently had another scroll related change - #27384 and not sure if there is any connection between them or not

@vladar
Copy link
Contributor

vladar commented Dec 9, 2020

The other PR was not touching the codepath with hashes. But yeah, subtle behavior changes are hard to foresee.

@pieh
Copy link
Contributor

pieh commented Dec 16, 2020

This went out in 2.29, so I'll close this PR as there is no point in having this open anymore

@pieh pieh closed this Dec 16, 2020
@LekoArts LekoArts deleted the backport-2.28-28555 branch April 23, 2021 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants