Hi Dan.
We’re aware of the uncomfortable behaviour and we’re already working on a solution.
In order to automatically scroll the viewport when the virtual keyboard opens, we need to know where the input caret is located. While this can be done pretty easily on Windows, X11 and macOS are quite limited and we’re still looking for the right way to retrieve that information. Any hints from our great community is more than welcome. 🙂
As you probably know, it is not possible to reduce the size of the virtual keyboard to grant more space to the remote desktop, but there are multiple ways to improve the input experience:
1. If you’re on iPad you can detach or split the keyboard and move it around by keeping the input spot visible.
2. You can zoom the area and move it above the keyboard (pinch out gesture to zoom, three fingers pan to move).
3. You can connect a bluetooth keyboard to the iPhone/iPad so the virtual keyboard will not be shown. Of course this is not the best solution on the move, but it’s worth to be mentioned. 🙂
At last, if you don’t use the extended keyboard you can disable it from Input settings and gain a few more valuable pixels.