Comment 4 for bug 1847318

I was thinking about this some more, and I think it is related to delays in the processing of events that we do. Currently, the selection actions for move-like commands do not use the position where the key was pressed but instead the position of the mouse when the actual selection functions are called. Unfortuantely, there are quite a few functions between the user pressing a key and these selection functions, and also there may be other events being processed that delay the key press event as well.

The best fix for this will be to modify the way we handle position information in these functions and use the position where the user pressed the key. This might be a fairly invasive change, so it might not make it back into 5.1. If it isn't as invasive as I think, then it could be backported after some testing in master (anything dealing with the tool framework seems to have some risk of introducing new problems).