When opening a heading through command palette (cmd+p) it seems to prioritize opening the heading in a tab that has the same file to which the heading to be opened belongs.
The problem is that there’s no history, so you can’t navigate back to the original offset (like it’s the case when doing the same from search results)
Related issue (unclear if the same or not)
Moved to help
@WhiteNoise thanks for taking a look at this. To clarify - I’m stating that changing the editor position (in this case by opening a different heading through command palette) should register in the navigation history and it’s not an this is the bug
As far as I can understand what you wrote, the existing feature request you linked is already asking for what you’ve put here. So this isn’t a “bug”. It’s just something that doesn’t exist. Please don’t open bugs to vote for a feature request. Go add a Like to the existing feature request and add your vote.
As far as I can understand what you wrote, the existing feature request you linked is already asking for what you’ve put here.
You didn’t understand. I said
Related issue (unclear if the same or not)
The behavior is inconsistent. Sometimes it works, sometimes it doesn’t. As a user I expect it to always work consistently - just like every other users that raised the same problem in the past.
The fact that one of the existing posting is marked as a feature does not make it a feature.
The feature is the navigation. It works the same way everywhere.
The bug is that navigation doesn’t work consistently.
BTW the same back button does work when clicking internal links in the embedded browser
see here Obsidian - Untitled 5 - obsidian-notes - Obsidian v1.8.6 - 15 February 2025 | Loom
Again - it’s standard UI behavior - it shouldn’t need definition, but nevertheless, here’s a more thorough treatment of what navigation means by Nielsen
@abuislam - thank you
yes, indeed that seems to be the issue. However, quite confusing as all links look and behave similarly, with just back navigation as an inconsistency.
I’ve found several posts on the forum, and there’s a plugin that seems to have a workaround - GitHub - pjeby/pane-relief: Obsidian plugin for per-pane history, pane movement/navigation hotkeys, and more.
The problem with plugins as workaround for bugs is that core functionality need a lot more context than an undocumented plugin interface and often break other things or performance. It’s like trying to fix a car through the exhaust 
.