Thanks. I can reproduce the issue. I’ll try to find out what’s going on. 

Thanks again for telling me about it! 

The issue was dependent on the screen width and didn't cause a problem on iPhone 16 Pro, so I didn't see that problem on my own device. It was also only a problem on iPhone, not on iPad.

Of course, this was kind of a rookie mistake. I'm not sure why I never noticed the fractional tab widths on iPhone. Looks like AutoLayout made sure that the subviews are positioned on pixel boundaries, so the images and labels were not blurred.

It looks like I used a fractional width for the tabs and forgot to round it to the next integer. 

On iPhone 13 mini, this resulted in a tab width of approximately 107.142857, which caused layout problems in the underlying UICollectionView.

When I now round the width to the next integer, the problem is gone.

This will be fixed in the next update.

I could now reproduce it in the iOS Simulator when selecting an iPhone 13 mini as the device and opening 8 tabs.

Thanks a lot for letting me know about this issue! I'll investigate what's going on.

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