Use case or problem
I have some really long files containing lots of headings, and many links to headings in other places within the file.
I would like to be able to use the forward/back buttons to quickly jump to a link, then return to where I was. This works perfectly with links to headings in other files but not to links to headings within the same file; no history marker is recorded when a link to a heading within the same file is followed.
Proposed solution
Record history markers when following links that point to places within the current file, so that the forward/back buttons can be used.
Related topics (optional)
7 Likes
The requested behavior is how web browsers behave, so there is precedent.
Renamed for clarity (was “History within files should be recorded”).
2 Likes
Yes, this would be cool. A flight recorder.
1 Like
Yes, this would be a really great fix. When I’m clicking around on links, unless I’m paying very close attention, I don’t even know whether the link is to another place in the same document or to another document, but I’ll click it and then click the “navigate back” arrow to, well, navigate back to where I was - but it doesn’t go there. Most of the time, it goes to some unrelated document where I happened to have been before I was in the document with the link. Now I’m just kinda lost, with the navigation arrows leaving me in a lurch with a gap where my intended destination is, so I am left to locate my self and get back by hand.
Even if I recognize the link is an intra-document link, that still doesn’t give me any options to get back. I either click the link and deal with it, or I don’t click the link.
A link is a link. You click one, you navigate away – whether to elsewhere in the document or to another document shouldn’t matter. And you need a reliable way to navigate back and forth in your chain of links. Right now, behavioral reliability isn’t there, leaving users to sometimes have to funnel with basic navigation while it’s handled perfectly at other times.
1 Like