tl;dr version of feedback
As it is currently implemented, I would honestly prefer the feature to be always off rather than always on. Right now, the synchronization is intrusive enough that it frequently works against my intent, forcing me to constantly fight the UI to maintain the context I want in each pane.
While losing click-to-navigate convenience would be a drawback, existing tools like Ctrl+F already provide a reliable way to locate content in either panel. That may require an extra step, but it is predictable and, more importantly, never overrides the user’s chosen viewport or focus unexpectedly.
I think the underlying idea is valuable, but it needs to become more intentional. A modifier key model (such as TeXMaker’s Cmd+Click) or a true link/unlink toggle would preserve the benefits of synchronized navigation while ensuring that users remain in control of when and how it occurs.
Full Feedback on Click-to-Navigate (Editor ↔ Preview) Feature
First, I want to say that I think this is a promising feature and a great addition to the editing experience. Being able to quickly jump between source and rendered output is genuinely useful. However, in its current implementation, the behavior feels a bit too aggressive because every click in either pane immediately forces the other pane to reposition.
In practice, I often want to edit one section of a document while simultaneously viewing a completely different section in the preview. For example, I may be making repetitive changes near the top of a file while monitoring formatting, equations, or generated output much further down. With the current behavior, any click resets that context and pulls the other window somewhere else, making it difficult to maintain separate working areas.
I would recommend considering one of the following approaches:
Option 1: Modifier Key Navigation (TeXMaker Style)
TeXMaker handles source-to-preview navigation by requiring a modifier key (for example, Cmd+Click) when the user explicitly wants to synchronize locations.
This approach has a few advantages:
- Normal clicks behave as expected and do not disrupt the other pane.
- Navigation remains available when needed.
- Accidental viewport jumps are greatly reduced.
- The intent to navigate is explicit rather than assumed.
Option 2: Linked/Unlinked Panes (Obsidian Style)
Another approach would be to allow users to toggle whether the editor and preview are linked.
When linked:
- Clicking in either pane navigates the other.
- Scrolling could optionally remain synchronized.
- The two views behave as a coordinated pair.
When unlinked:
- Each pane maintains its own position independently.
- Users can edit one section while viewing another.
- Navigation synchronization is temporarily disabled.
If a link/unlink model is used, I would expect it to apply to both navigation and scrolling behavior. Otherwise, users may end up in a confusing middle ground where current-line focus is synchronized but viewport position is not.
Why This Matters
A particular challenge arises when there is a large mismatch between source size and rendered output size. Some elements require extensive source code but generate relatively little visible output. In those situations, selecting or editing a small section of code can cause unexpectedly large movements in the preview viewport.
This is actually the same issue I encounter in Obsidian, and it is one of the main reasons I consider unlinking the panes essential. Without a way to temporarily decouple the views, the editor can feel like it’s fighting the user’s intent rather than helping them navigate.
Overall
I think the feature is valuable and worth keeping, but the current “always synchronized” model is too aggressive for many real-world editing workflows. A modifier-key approach like TeXMaker’s Cmd+Click, or a clear link/unlink toggle similar to Obsidian’s pane model, would provide users with much more control while preserving the benefits of quick source-to-preview navigation.
, 
, or