Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Remember scroll position of md.files in Canvas #86

Open
Pixel3ro opened this issue Jul 6, 2024 · 1 comment
Open

[FR] Remember scroll position of md.files in Canvas #86

Pixel3ro opened this issue Jul 6, 2024 · 1 comment
Labels
feature request New feature or request low-priority

Comments

@Pixel3ro
Copy link

Pixel3ro commented Jul 6, 2024

Single-tab file traversal: i I'm working in a Canvas. > ii I click a file link in the Canvas. > iii The file opens in the same tab, replacing the Canvas view. > iv When I'm done with the file, I click the "back" button to return to the Canvas. (back to 'i')

issue: when I get back to the Canvas, it doesn't remember Scroll Position of any file as it was in i. Resetting scroll positions of all files to the top and I lose my familiar viewing position.
Oftentimes I accidentally open files in Full-Editor (double-clicking file-name while trying to enable cursor), and I quickly get back to the Canvas to resume work. But it looks unfamiliar at the blink of an eye as the scroll-config has changed, forcing me to find where I left-off, making it hard to resume work instantly.
As it affects all the files in the Canvas, i run into this often while panning across the Canvas, and breaks my flow often. I'm highly penalized for just one accidental double-click.

PS: this is not about resuming-position (view coordinate and zoom) in the Canvas. It is to do only with .md files and their individual scroll positions.

@Developer-Mike
Copy link
Owner

This feature can potentially be added. I need to look at the difficulties of implementing this function though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request low-priority
Projects
None yet
Development

No branches or pull requests

2 participants