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

Feature request for Web: Save position between preview and editor and vice versa #105

Open
ghost opened this issue Jan 16, 2021 · 11 comments

Comments

@ghost
Copy link

ghost commented Jan 16, 2021

  • Open a note and write more than fits on your screen
  • Scroll down to the bottom and click Preview

==> Previous starts at the top of the note

Would be nice if Previous shows me where I was writing.

Similar:

  • Scroll down in preview mode and press Edit

==> Editor starts at the top of the document

Would be nice if editor shows me the part of the note I was looking at in preview.

It would make it much easier when writing longer notes and needing to, for example, check formatting of markdown, or wanting to make sure it is regularly saved.

Thanks!

@tasn
Copy link
Member

tasn commented Jan 17, 2021

Thanks for opening the ticket, it's actually not trivial (because of different sizing), but it's something we plan on taking a look at at some point.

@ghost
Copy link
Author

ghost commented Jan 17, 2021 via email

@tasn
Copy link
Member

tasn commented Jan 17, 2021

I think @zecakeh spent quite a bit of time thinking about this, so maybe he can provide some input.

@zecakeh
Copy link
Contributor

zecakeh commented Jan 17, 2021

I haven't really looked at it in native mode. At the time it was inside a webview.

However, it should be trivial if we store the scroll position from the scrollview in state as a relative position and use it when we switch view.

@tasn
Copy link
Member

tasn commented Jan 17, 2021

It's not as simple as storing the scroll position. A better bet would probably be to store the proportional scroll position (e.g. 30%), though even that will be massively skewed due to titles and images.

@zecakeh
Copy link
Contributor

zecakeh commented Jan 17, 2021

I know it'll probably be skewed, but it's better than nothing. I think overall it should be a better experience than without that.

@tasn
Copy link
Member

tasn commented Jan 17, 2021

Probably.

@Salt-Factory
Copy link

I'd like something similar, but instead of scrolling to where you were in the other mode, I'd like it to scroll back to where it was before I switched out of the mode.
This functionality partially overlaps with the one described above.

E.g., say I am looking at the third paragraph of my text in view mode and I notice a typo. I switch to edit mode, fix the typo, and then switch back to view mode, where instead of showing me the top of the text, it shows me where I left off (which is paragraph 3).

I think most people have a similar style of working, where they edit something and then switch back. Or where they add a new paragraph 4, and then check view mode to see what it looks like. The proposed functionality would then show paragraph 3 (because that's what we last looked at in view mode), which is right above our new paragraph.

@ghost
Copy link
Author

ghost commented Mar 16, 2021

Another, related, request that may need its own ticket(?): Can also the scroll position be saved between notes list and note content?

  1. See notes list
  2. Scroll down to select a note
  3. Open the note
  4. Maybe switch into note, edit something small, then preview, then go back to notes list

==> currently I'm at the top of the notes list

It would be ideal if the scroll position of notes list could be saved, so I don't need to scroll down and find where I was.

NOTE: This already works after using Search. Scroll position is saved if I searched for something previous and open note after a search and then go back.

@zecakeh
Copy link
Contributor

zecakeh commented Mar 16, 2021

I believe it's better if it's in its own ticket since those will be implemented separately

@ghost
Copy link
Author

ghost commented Mar 16, 2021

OK thanks, created a new one for that one

#172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants