Ok. Which iOS version are you running?

First I need to be able to reproduce the issue.

Does it depend on the number of open tabs? Or does it also happen with just two or three tabs?

Thanks for the video! I can see the problem in the video and tried to reproduce it on my iPhone.

Unfortunately, I could not reproduce it. I tried opening a lot of files in tabs, but I never see the problem that is shown in the video.

First of all, can you please try if a reboot of your iPhone changes the behavior?

Are there any special settings you have enabled on your iPhone - e.g. accessibilty settings or dynamic type? I already tried enabling the "Bold text" accessibility settings, but that didn't cause a problem.

This is now implemented in Textastic 10.7.1 which was just released on the App Store:

Tapping the editor to bring up the on-screen keyboard now scrolls the tapped line into view if it would otherwise be hidden behind the keyboard.

I've reported this bug to Apple.

I've been debugging the problem and this looks like an actual iOS bug.

I can reproduce the same behavior in the Notes app and in Runestone on iPadOS 18.5.

I don't think I can work around this problem because this appears to be a bug in the iOS text system.

Can you also see the problem in the Notes app?

• Open a note in the Notes app
• Place the insertion point at the start of a line
• Use Shift-Arrow Down to select the current line
• Press Arrow Up
• Now the insertion point is at the beginning of the document

Sorry, my previous answer was for the iOS version of Textastic, but you seem to be asking for the Mac version of Textastic.

Use File -> Open… to open a folder and add it to the sidebar. Alternatively, you can drag and drop folders from Finder to Textastic's Dock icon to add it to the sidebar.

Cmd-C isn't even necessary: just Shift-Cursor Down to select the whole line and then Cursor Up jumps to the start of the file. 

But then pressing down again jumps to the next line as expected.

I hope it's easy to fix.

Thanks! With these instructions I could reproduce it!

Never noticed this before. That's a nasty bug - I'll investigate.

Hmm. I just tried to reproduce this, but for me it behaves as expected. 

Are you sure that you are not just pressing Cursor up when you are already pressing the Cmd key for Cmd-C?

Can you maybe make a deliberate short pause between pressing Shift-Cursor Up and Cmd-C to see if this is indeed an issue with the app?

How is the behavior in other apps - e.g Apple's Notes or another editor app like Runestone?

I'm really not doing anything special with these keyboard shortcuts and Cmd-C and Shift-Cursor up are iOS system shortcuts.