I think you are talking about this 🐛 #422, aren't you?

The two issues are closely related, but the descriptions of how to proceed are different.

• routing bug #422: Do stuff when I change the scroll position (update the sidebar and/or URL on page scroll)
• Always scroll to clicked sidebar content #522: Change the scroll position when I do stuff (click an already active sidebar link)

I believe the fix for this issue is straightforward: when a user clicks a link in the sidebar, always scroll that content into view at the top of the viewport--even if it's the active link / URL. If a user clicks a sidebar link, then waits for the content to scroll into view, then scrolls 10 pixels, clicking the same sidebar link should scroll the content back 10px to the initial scroll position. That's it.

For #422, I agree that the sidebar should always reflect the current scroll position of the page: as the user scrolls, the active link in the sidebar should be highlighted in all scenarios. I do not , however, think the URL should be updated as the page is scrolled. Instead, the URL should be updated only when a user-initiated navigation action has occurred (i.e. clicking a sidebar link).

+1 to this.

I can manual fix it creating links with full parameters in href value.

For example, if my first heading in a sample.md page is "01. Introduction", I could achieve page change and reset scroll position with this link:

[My Link](/sample.md?id=_01-introduction)

But it could be perfect that changing section always reset scroll position to the top, is natural behaviour when changing the main content.

A colateral issue with this approach appears when I attempt to replicate this behaviour on sidebar.md links, I get wrong subnavigation rendering (subnavigation is attached under main navigation item that is not the selected one).

I think this has been fixed in develop.

is there an update on this?

hi, also checking if this has been fixed? seems like a bug that really hurts the UX .. is there a common/easy solution?

Hey all, I believe this is the configuration parameter that is required to be changed from the default:
https://docsify.js.org/#/configuration?id=auto2top

Still seeing this bug. Even with config of auto2top=true set.