Add example of modify state of query string

[dxinteractive]

But we need to deal with this gatsby bug first gatsbyjs/gatsby#12997. For some reason gatsby jumps to the top of the page if you modify the query string and dont change routes

[narration-sd]

@dxinteractive Could have to do with what I noticed here: gatsbyjs/gatsby#12560 (comment)

I suspect the Gatsby scroll memory isn't quite doing what's needed or expected yet. There has seemed an emphasis on vocal requests for always return-to-top behaviour, and perhaps that has influenced whether the overall system is being assured to do also as others need.

[dxinteractive]

Ah thanks for the heads up @narration-sd - yeah I agree with what you've found, although I think I'll need to dive into how it all works to understand your observations fully.

I attempted to work around this by using shouldUpdateScroll in gatsby's browser APIs, as it gives enough information for me to dictate when a scroll position should change or not, but I couldn't use it because returning true from that function does not always result in default behaviour - contrary to what they claim: https://www.gatsbyjs.org/docs/browser-apis/#shouldUpdateScroll

I'm yet to file a bug on that because I need to redo it and find out exactly which situations it wasn't working with, and it's been too long so I can't remember :)