@Mark-Olson said in Menu command for ensuring current position is visible:

I agree with you that this is pretty confusing, and agree that using the arrow keys should have the same effect as typing. This would obviously be a separate feature request though, and as you noted I rather doubt that it would be accepted because it would only add confusion for some other users.

After sleeping one night about it, and rereading your posting about typing any char and undo. Also in your issue #17297 and @Alan-Kilborn 's issue #12107 … I have changed my mind a bit, because I think that both situations of keystrokes (typing char from keyboard input or pressing arrow key) should be handled in the same way. This would make consistent behaviour of the application.

I think, keystrokes should always have direct effect on a visible caret, so the caret should be made visible first, and afterwards perform the action from keyboard (typing char/moving caret).

Keystrokes on an invisible caret look more like undefined behaviour. The user does not know, where his focus is. Even making caret jump to next visible position could be unexpected, because user did not know where he previously has been. Maybe user is even confused, because of the jump.

So from this perspective, the current behaviour of arrow keys could be worth considering if it is unexpected/inconsistent.