Retaining caret and scroll position when delving into and coming out of a bullet point doesn't happen on iOS

On macOS, when you zoom in on a bullet point and then you come back, the scroll position is restored and the caret retains its position. This is ok.

However on iOS, zooming in and then coming back either through the back gesture or through the breadcrumb results in the scroll going to the very top. I understand that it doesn't make much sense to remember the caret position on a touch device where the keyboard keeps hiding, but the scroll position should be restored.

Doing this will not only make the iOS app in parity with the macOS app but it will also make it more native: Bear remembers scroll position while Obsidian doesn't. Please see this post

Thanks for pointing this out. I’ve fixed this in the upcoming 1.20 release.

In 1.20, the previous scroll position is restored when navigating back on iOS. If you use Home again while already at the root, it scrolls to the top. There are still some cases where the scroll position isn’t restored correctly, and I’m working on improving them.

Version 1.20.0 is still under review and hasn’t been released yet. If you’d like to try it, I can send you a TestFlight invitation.

The blog post was helpful too, and I appreciate this kind of detailed feedback.

Yes please — send me a TestFlight invitation on my forum's sign in email.

Thanks for confirming. I’ve added you to the beta group and sent a TestFlight invitation. Please check your email for the invitation.

The beta app uses separate data from the production app.

Verified that the change is working on iOS. It doesn't persist positions when the app is closed/removed from memory and then reopened, but the change is an improvement from what we had before!

There are still some cases where the scroll position isn’t restored correctly, and I’m working on improving them.

Let me know what these cases are and when you fix them so I can test them out.

Thanks for confirming and for the helpful feedback.

I’m currently aware of two issues. Navigating to another view through a tag or similar does not restore the previous scroll position. On iOS, moving forward from Home after going back resets the scroll position to the top.

For 1.21, I’ll work on these two issues and also try to restore the scroll position after restarting the app, as you suggested.

Thanks again for your help.

.

and also try to restore the scroll position after restarting the app

Thanks for considering it. In case you implement it for iOS, please implement the same for macOS as well.

Edit: I just realised that Kosshi on Mac can have multiple windows open. That makes me less sure of having the "scroll position after restarting the app" feature on macOS.

I also checked Bear on macOS — it only remembers scroll position while the app is open. Once it is completely closed (quit) and reopened, the scroll positions on macOS go away.

I think restoring the scroll position after restarting the app is needed on iOS because iOS evicts apps from memory fairly quickly, but is not needed on macOS

One thing I noticed on macOS 1.20.0 Beta app is when I zoom-in into a bullet and come out of it, the cursor position isn't maintained.

Here's me demonstrating wrt Bike which does that.

Do you want me to file this improvement as a separate ticket?

Thanks for the helpful follow-up and for sharing the video.

1. Scroll position

For macOS, I agree that preserving the scroll position separately for each window while navigating would be more convenient. I’ll look into implementing it that way.

2. Cursor position

Thank you for pointing this out as well. The cursor position is lost when leaving a zoomed-in bullet on macOS, so I’ll work on this together with the scroll position issue.

I’ll take care of both issues here, so there’s no need to file a separate ticket.

1. Scroll position
For macOS, I agree that preserving the scroll position separately for each window while navigating would be more convenient. I’ll look into implementing it that way.

Oh maybe I wasn't clear. It was just me thinking out loud and realising that Kosshi has panes and windows. I am not asking to preserve scroll position per window and pane at all. This would add unnecessary work for you.

Please only look into point 2, 2. Cursor position, and fixing these iOS issues

Thanks for clarifying, Ajit. For now, I’ll focus on the cursor position issue and the linked iOS issues.