Hi Coda team,
I’d love to see published docs treat internal “jump-to” links as full navigations in the browser history. Right now, clicking a link to a heading smoothly scrolls and updates the URL without pushing a new history entry, so the Back button skips past all my in-page jumps and exits the document entirely.
Proposed behavior:
When an anchor link is clicked in a published document, call history.pushState (not replaceState) before scrolling. That way each jump-to-heading becomes its own entry in the browser history, and users can step backward through every internal link click.
This would make Fragment URLs behave just like classic HTML anchors, improving usability for long documents and shared links. Thanks for considering it!