sendKeyStroke functions differently depending on if the user has num lock enabled or disabled. If num lock is disabled, the key strokes seem to act appropriately. But if num lock is enabled, the function sends unexpected keys.
For reference, our app is sending
down key strokes. If the user has num lock enabled then instead of the expected results we see a series of numbers and decimals, as if the user was pressing a corresponding key on the numpad.
 I wasn’t able to find documentation on the accepted input for the
keyString parameter, so if these values are unexpected please let us know.
Steps to reproduce:
sendKeyStroke("up") with num lock disabled, and observe the expected results. Enable num and observe that OW sends an
8 keystroke instead.
Impact for my app: [low, mid, high, show-stopper]
Low - users can work around the issue by disabling num lock, it’s just an inconvenience.